Files
k8scd/velero/velero-helm.yaml
T
Ruben Hensen e19f4b8db5 velero: skip the CRD upgrade hook
The hook's init container pulls docker.io/bitnami/kubectl:1.32, which
Bitnami has removed, so the sync for the new NAS address hung on
ImagePullBackOff. The chart stays at 8.4.0 and the CRDs are already in
place.
2026-10-21 12:22:57 +02:00

66 lines
2.0 KiB
YAML

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: velero-helm
namespace: argocd
spec:
project: default
source:
chart: velero
repoURL: https://vmware-tanzu.github.io/helm-charts
targetRevision: 8.4.0
helm:
values: |
# The CRD upgrade hook pulls docker.io/bitnami/kubectl, which Bitnami
# has removed, so every sync hangs on it. The CRDs only change with
# the chart version; turn this back on (with another kubectl image)
# when bumping targetRevision.
upgradeCRDs: false
initContainers:
- name: velero-plugin-for-aws
image: velero/velero-plugin-for-aws:v1.11.1
volumeMounts:
- mountPath: /target
name: plugins
configuration:
backupStorageLocation:
- name: default
bucket: velero-backups
provider: aws
config:
region: minio
s3ForcePathStyle: true
s3Url: http://192.168.1.10:9000
insecureSkipTLSVerify: "true"
volumeSnapshotLocation:
- name: default
provider: aws
config:
region: minio
features: EnableCSI
credentials:
# Use existing secret created by External Secrets Operator
# existingSecret: velero-minio-credentials
# extraEnvVars:
# AWS_SHARED_CREDENTIALS_FILE: /credentials/cloud
existingSecret: cloud-credentials
deployNodeAgent: true
nodeAgent:
containerSecurityContext:
privileged: true
resources:
requests:
cpu: 100m
memory: 256Mi
limits:
cpu: 500m
memory: 512Mi
destination:
server: https://kubernetes.default.svc
namespace: velero
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true