molgenis-ops-docker-helm/molgenis-vault/resources/restore.yaml

# Use kubectl create -f restore.yaml to manually execute a restore of the vault
apiVersion: "etcd.database.coreos.com/v1beta2"
kind: "EtcdRestore"
metadata:
  # The restore CR name must be the same as spec.etcdCluster.name
  name: vault-etcd
  namespace: vault-operator
spec:
  etcdCluster:
    # The namespace is the same as this EtcdRestore CR
    name: vault-etcd
  backupStorageType: S3
  s3:
    path: vault/backup-<name>
    awsSecret: aws
    endpoint: http://minio.minio.svc:9000
feat (molgenis-vault): Add backup cronjob Needs to run under service account created by the etcd-operator subchart so there's some template magic needed to figure out what it's called. 2018-09-07 16:09:15 +02:00			`# Use kubectl create -f restore.yaml to manually execute a restore of the vault`
feat (molgenis-vault): Use vault-operator chart and etcd-operator chart to deploy a vault with backup secret. 2018-09-07 15:13:00 +02:00			`apiVersion: "etcd.database.coreos.com/v1beta2"`
			`kind: "EtcdRestore"`
			`metadata:`
			`# The restore CR name must be the same as spec.etcdCluster.name`
			`name: vault-etcd`
			`namespace: vault-operator`
			`spec:`
			`etcdCluster:`
			`# The namespace is the same as this EtcdRestore CR`
			`name: vault-etcd`
feat (molgenis-vault): Switch backup storage to s3. We can host s3 compatible storage locally by deploying the stable/minio chart. Ran into https://github.com/coreos/etcd-operator/issues/1980 and therefore downgrade the backup and restore operator images to 0.8.3. 2018-09-17 00:27:50 +02:00			`backupStorageType: S3`
			`s3:`
			`path: vault/backup-<name>`
			`awsSecret: aws`
			`endpoint: http://minio.minio.svc:9000`