Files
k8scd/velero/velero-helm.yaml
T
Ruben Hensen 8c2bd89444 Point Velero and the NAS services at 192.168.1.10
The NAS moved from 192.168.1.99 to .10, so the backup storage location
has been Unavailable ("no route to host"). Every backup since at least
26 July failed, and 154 expired ones are stuck in Deleting because Velero
can't reach the bucket to remove them. MinIO answers on .10:9000 and DSM
on .10:5000.
2026-10-21 12:16:19 +02:00

61 lines
1.7 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: |
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