Skip to content


Folders and files

Last commit message
Last commit date

Latest commit



90 Commits

Repository files navigation


Docker Repository on Quay Docker Repository on Docker Hub

Quick 'n dirty kubernetes state backup script, designed to be ran as kubernetes Job. Think of it like RANCID for kubernetes.

Props to @gianrubio for coming up with the idea.


Use the deployment example (ssh or AWS CodeCommit authentication) and deploy a kubernetes CronJob primitive in your kubernetes (1.5 and up) cluster ensuring backups of kubernetes resource definitions to your private git repo.

Define the following environment parameters:

  • GIT_REPO - GIT repo url. Required
  • GIT_PREFIX_PATH - Path to the subdirectory in your repository. Default: .
  • NAMESPACES - List of namespaces to export. Default: all
  • GLOBALRESOURCES - List of global resource types to export. Default: namespace
  • RESOURCETYPES - List of resource types to export. Default: ingress deployment configmap svc rc ds networkpolicy statefulset storageclass cronjob. Notice that Secret objects are intentionally not exported by default (see git-crypt section for details).
  • GIT_USERNAME - Display name of git user. Default: kube-backup
  • GIT_EMAIL - Email address of git user. Default:
  • GIT_BRANCH - Use a specific git branch . Default: master
  • GITCRYPT_ENABLE - Use git-crypt for data encryption. See git-crypt section for details. Default: false
  • GITCRYPT_PRIVATE_KEY - Path to private gpg key for git-crypt. See git-crypt section for details. Default: /secrets/gpg-private.key
  • GITCRYPT_SYMMETRIC_KEY - Path to shared symmetric key for git-crypt. See git-crypt section. Default: /secrets/symmetric.key

Choose one of two authentication mechanisms:

  • When using AWS CodeCommit and policy-based access from AWS, modify your cluster configuration to provide GitPull and GitPush access for that CodeCommit repo to your cluster. If using kops, the configuration will look something like this:
    node: |
          "Effect": "Allow",
          "Action": [
          "Resource": "arn:aws:codecommit:<region>:<account name>:<repo-name>"

NOTE: in this deployment, the ssh volume and secret are not present.

  • When using a different repository (GitHub, BitBucket, etc.), mount a configured ssh directory in /backup/.ssh with the following files:

    • known_hosts - Preloaded with SSH host key of $GIT_REPO host.
    • id_rsa - SSH private key of user allowed to push to $GIT_REPO.

Easiest way of doing this is:

ssh-keygen -f ./id_rsa
ssh-keyscan $YOUR_GIT_HOST > known_hosts

kubectl create secret generic kube-backup-ssh -n kube-system --from-file=id_rsa --from-file=known_hosts

NOTE: If id_rsa isn't found in your ssh directory, the backup script will assume you're using AWS CodeCommit.


  • Modify the snapshot frequency in spec.schedule using the cron format.
  • Modify the number of successful and failed finished jobs to retain in spec.successfulJobsHistoryLimit and spec.failedJobsHistoryLimit.
  • If using RBAC (1.6+), use the ClusterRole and ClusterRoleBindings in rbac.yaml.


For security reasons Secret objects are not exported by default. However there is a possibility to store them safely using the git-crypt project.


Your repository has to be already initialized with git-crypt. Minimal configuration is listed below. For details and full information see using git-crypt.

cd repo
git-crypt init
cat <<EOF > .gitattributes
*.secret.yaml filter=git-crypt diff=git-crypt
.gitattributes !filter !diff
git-crypt add-gpg-user <USER_ID>
git add -A
git commit -a -m "initialize git-crypt"


  • You may choose any subdirectory for storing .gitattributes file (useful when using GIT_PREFIX_PATH).
  • You may encrypt additional files other than secret.yaml. Add additional lines before the .gitattribute filter. You may also use wildcard * to encrypt all files within the directory.

Enable git-crypt

To enable encryption feature:

  • Set pod environment variable GITCRYPT_ENABLE to true

      - env:
        - name: GITCRYPT_ENABLE
          value: "true"
  • Create additional Secret object containing either gpg-private or symmetric key

    apiVersion: v1
    kind: Secret
      name: kube-backup-gpg
      namespace: kube-system
      gpg-private.key: <base64_encoded_key>
      symmetric.key: <base64_encoded_key>
  • Mount keys from Secret as additional volume

      - volumeMounts:
        - mountPath: /secrets
          name: gpgkey
      - name: gpgkey
          defaultMode: 420
          secretName: kube-backup-gpg
  • Add secret object name to RESOURCETYPES variable

      - env:
        - name: RESOURCETYPES
          value: "ingress deployment configmap secret svc rc ds thirdpartyresource networkpolicy statefulset storageclass cronjob"
  • If using RBAC (1.6+), add secrets to resources

    - apiGroups: ["*"]
      resources: [
  • (Optional): $GITCRYPT_PRIVATE_KEY and $GITCRYPT_SYMMETRIC_KEY variables are the combination of path where Secret volume is mounted and the name of item key from that object. If you change any value of them from the above example you may need to set this variables accordingly.


All configured resources will be exported into a directory tree structure in YAML format following a $namespace/$name.$type.yaml file structure.

β”œβ”€β”€ kube-system
β”‚Β Β  β”œβ”€β”€ attachdetach-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ canal-config.configmap.yaml
β”‚Β Β  β”œβ”€β”€ canal.daemonset.yaml
β”‚Β Β  β”œβ”€β”€ canal.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ certificate-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ cronjob-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ daemon-set-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ default.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ deployment-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ disruption-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ dns-controller.deployment.yaml
β”‚Β Β  β”œβ”€β”€ dns-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ endpoint-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ generic-garbage-collector.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ horizontal-pod-autoscaler.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ job-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ kube-backup-gpg.secret.yaml
β”‚Β Β  β”œβ”€β”€ kube-backup.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ kube-backup-ssh.secret.yaml
β”‚Β Β  β”œβ”€β”€ kube-dns-autoscaler.configmap.yaml
β”‚Β Β  β”œβ”€β”€ kube-dns-autoscaler.deployment.yaml
β”‚Β Β  β”œβ”€β”€ kube-dns-autoscaler.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ kube-dns.deployment.yaml
β”‚Β Β  β”œβ”€β”€ kube-dns.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ kube-dns.service.yaml
β”‚Β Β  β”œβ”€β”€ kubelet.service.yaml
β”‚Β Β  β”œβ”€β”€ kube-prometheus-exporter-kube-controller-manager.service.yaml
β”‚Β Β  β”œβ”€β”€ kube-prometheus-exporter-kube-dns.service.yaml
β”‚Β Β  β”œβ”€β”€ kube-prometheus-exporter-kube-etcd.service.yaml
β”‚Β Β  β”œβ”€β”€ kube-prometheus-exporter-kube-scheduler.service.yaml
β”‚Β Β  β”œβ”€β”€ kube-proxy.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ kube-state-backup-new.cronjob.yaml
β”‚Β Β  β”œβ”€β”€ kube-sysctl.daemonset.yaml
β”‚Β Β  β”œβ”€β”€ letsencrypt-prod.secret.yaml
β”‚Β Β  β”œβ”€β”€ namespace-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ node-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ openvpn-ccd.configmap.yaml
β”‚Β Β  β”œβ”€β”€ openvpn-crl.configmap.yaml
β”‚Β Β  β”œβ”€β”€ openvpn.deployment.yaml
β”‚Β Β  β”œβ”€β”€ openvpn-ingress.service.yaml
β”‚Β Β  β”œβ”€β”€ openvpn-pki.secret.yaml
β”‚Β Β  β”œβ”€β”€ openvpn-portmapping.configmap.yaml
β”‚Β Β  β”œβ”€β”€ openvpn-settings.configmap.yaml
β”‚Β Β  β”œβ”€β”€ persistent-volume-binder.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ pod-garbage-collector.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ replicaset-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ replication-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ resourcequota-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ route53-config.secret.yaml
β”‚Β Β  β”œβ”€β”€ service-account-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ service-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ statefulset-controller.serviceaccounts.yaml
β”‚Β Β  β”œβ”€β”€ sysctl-options.configmap.yaml
β”‚Β Β  β”œβ”€β”€ tiller-deploy.deployment.yaml
β”‚Β Β  β”œβ”€β”€ tiller-deploy.service.yaml
β”‚Β Β  β”œβ”€β”€ tiller.serviceaccounts.yaml
β”‚Β Β  └── ttl-controller.serviceaccounts.yaml
β”œβ”€β”€ prd
β”‚Β Β  β”œβ”€β”€ initdb.configmap.yaml
β”‚Β Β  β”œβ”€β”€ example-app.deployment.yaml
β”‚Β Β  β”œβ”€β”€ example-app.ingress.yaml
β”‚Β Β  β”œβ”€β”€ example-app.secret.yaml
β”‚Β Β  β”œβ”€β”€ example-app.service.yaml
β”‚Β Β  β”œβ”€β”€ postgres-admin.secret.yaml
β”‚Β Β  β”œβ”€β”€ postgresql.deployment.yaml
β”‚Β Β  β”œβ”€β”€ postgresql.service.yaml
β”‚Β Β  β”œβ”€β”€ postgres.secret.yaml
β”‚Β Β  β”œβ”€β”€
β”‚Β Β  β”œβ”€β”€ redis.service.yaml
β”‚Β Β  └── redis-standalone.rc.yaml
└── staging
 Β Β  β”œβ”€β”€ initdb.configmap.yaml
 Β Β  β”œβ”€β”€ example-app.deployment.yaml
 Β Β  β”œβ”€β”€ example-app.ingress.yaml
 Β Β  β”œβ”€β”€ example-app.secret.yaml
 Β Β  β”œβ”€β”€ example-app.service.yaml
 Β Β  β”œβ”€β”€ postgres-admin.secret.yaml
 Β Β  β”œβ”€β”€ postgresql.deployment.yaml
 Β Β  β”œβ”€β”€ postgresql.service.yaml
 Β Β  β”œβ”€β”€ postgres.secret.yaml
 Β Β  β”œβ”€β”€
 Β Β  β”œβ”€β”€ redis.service.yaml
 Β Β  └── redis-standalone.rc.yaml

3 directories, 80 files

This project is MIT licensed.