Files
k8scd/velero/velero-helm.yaml
T
Ruben Hensen 6d9e405126 Point Velero and the NAS services back at 192.168.1.99
Reverts 8c2bd89. The NAS had fallen back to a DHCP address (.10), which
also moved the UniFi controller it hosts away from where the gateway
and access points inform, and left the Longhorn backup target at
nfs://192.168.1.99 unreachable. It now has 192.168.1.99 set statically
in DSM again, so everything that pointed at .99 works without changes.
2026-10-21 15:25:16 +02:00

68 lines
2.1 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.99: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
# 512Mi got the server OOMKilled 314 times, including halfway
# through a backup of ~14.7k items.
resources:
requests:
cpu: 100m
memory: 512Mi
limits:
cpu: 500m
memory: 2Gi
destination:
server: https://kubernetes.default.svc
namespace: velero
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true