Katafygio

Katafygio records Kubernetes objects as YAML files in a Git repository. That gives operators a history of changes to resources such as Deployments and Services, and a way to recover selected declarations later. It is useful for configuration visibility or reconstruction, but it does not capture the application data stored in databases or volumes. The object selection also matters: accidentally recording Secrets can leave sensitive values permanently present in Git history.

Current guidance

The recovered marketplace URL is not the project’s primary documentation. The historical stable chart identifies bpineau/katafygio, whose README describes one-off dumps and continuous recording of Kubernetes objects as YAML in Git. The current upstream also documents its own chart repository, distinct from the retired central stable chart.

Choose the objects to include before enabling remote pushes. The upstream examples explicitly exclude Secrets, noisy events and controller-owned objects. Kubernetes Secrets encoded in YAML are not encrypted simply because their values use base64; accidental inclusion can persist sensitive data in Git history after the current file is deleted.

Decide whether this history is an audit record or a source for reconstruction, and avoid feeding generated controller state back into an independent GitOps reconciler. Test restoring a small application’s declarative resources into an isolated namespace and document the dependencies that must exist first. Back up persistent-volume data, external databases and credentials through appropriate separate mechanisms. A complete YAML dump cannot establish that an application’s data can be recovered or that its old API versions remain accepted.