You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2020. It is now read-only.
Backup operator ignoring maxbackups setting and creating new blobs without deleting the old one.
blob format: etcd.backup_v3_2019-12-15-15:57:59
This is running on AKS K8s version 1.14.8, storage account type: BlobStorage
etcdbackup definintion:
apiVersion: "etcd.database.coreos.com/v1beta2"
kind: "EtcdBackup"
metadata:
name: example-etcd-cluster-1-backup
namespace: admin
spec:
backupPolicy:
backupIntervalInSecond: 125
maxBackups: 4
etcdEndpoints: ["http://example-etcd-cluster-1-client:2379"]
storageType: ABS
abs:
# The format of the path must be: "<abs-container-name>/<path-to-backup-file>"
path: etcd-backups/etcd.backup
absSecret: abs-credentials
error in cr status (but backup still works):
status:
Reason: 'failed to save snapshot (create etcd client failed: failed to get etcd
client with maximum kv store revision: could not create an etcd client for the
max revision purpose from given endpoints ([http://example-etcd-cluster-1-client:2379]))'
etcdRevision: 3
etcdVersion: 3.2.13
lastSuccessDate: "2019-12-15T16:12:34Z"
succeeded: false
The text was updated successfully, but these errors were encountered:
rhollins
changed the title
backup-operator - ABS - backupPolicy - maxBackups doesn't cleanup old backup blobs
backup-operator - ABS - backupPolicy - maxBackups doesn't cleanup old backup blobs in Azure SA account
Dec 15, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Backup operator ignoring maxbackups setting and creating new blobs without deleting the old one.
blob format: etcd.backup_v3_2019-12-15-15:57:59
This is running on AKS K8s version 1.14.8, storage account type: BlobStorage
etcdbackup definintion:
error in cr status (but backup still works):
The text was updated successfully, but these errors were encountered: