kube-backup | : floppy_disk : Kubernetes resource state sync to git | Continuous Backup library

Use the deployment example ([ssh](cronjob-ssh.yaml) or [AWS CodeCommit](cronjob-codecommit.yaml) 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](#git-crypt) for details). * GIT_USERNAME - Display name of git user. Default: kube-backup * GIT_EMAIL - Email address of git user. Default: kube-backup@example.com * GIT_BRANCH - Use a specific git branch . Default: master * GITCRYPT_ENABLE - Use git-crypt for data encryption. See [git-crypt section](#git-crypt) for details. Default: false * GITCRYPT_PRIVATE_KEY - Path to private gpg key for git-crypt. See [git-crypt section](#git-crypt) for details. Default: /secrets/gpg-private.key * GITCRYPT_SYMMETRIC_KEY - Path to shared symmetric key for git-crypt. See [git-crypt section](#git-crypt). Default: /secrets/symmetric.key.
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: ```yaml additionalPolicies: node: | [ { "Effect": "Allow", "Action": [ "codecommit:GitPull", "codecommit:GitPush" ], "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: ```bash 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.