Scheduled snapshots for Kubernetes persistent volumes
:warning: Helm chart now directly manages CRD installation/upgrade. If upgrading from 3.1.0 or earlier, manual steps are required:
Error: UPGRADE FAILED: rendered manifests contain a resource that already
exists. Unable to continue with update: CustomResourceDefinition
"snapshotschedules.snapscheduler.backube" in namespace "" exists and cannot be
imported into the current release: invalid ownership metadata; label
validation error: missing key "app.kubernetes.io/managed-by": must be set to
"Helm"; annotation validation error: missing key "meta.helm.sh/release-name":
must be set to "snapscheduler"; annotation validation error: missing key
"meta.helm.sh/release-namespace": must be set to "backube-snapscheduler"
The above error can be fixed by adding the required labels and annotations as mentioned in the error message:
$ kubectl label crd/snapshotschedules.snapscheduler.backube app.kubernetes.io/managed-by=Helm
customresourcedefinition.apiextensions.k8s.io/snapshotschedules.snapscheduler.backube labeled
$ kubectl annotate crd/snapshotschedules.snapscheduler.backube meta.helm.sh/release-name=snapscheduler
customresourcedefinition.apiextensions.k8s.io/snapshotschedules.snapscheduler.backube annotated
$ kubectl annotate crd/snapshotschedules.snapscheduler.backube meta.helm.sh/release-namespace=backube-snapscheduler
customresourcedefinition.apiextensions.k8s.io/snapshotschedules.snapscheduler.backube annotated
Made CRD validation of cronspec more permissive
Upgrade quay.io/brancz/kube-rbac-proxy to v0.13.1
Upgrade operator-sdk to 1.23.0