fix(csi-driver-nfs): remove redundant velero crap from values.yaml

This commit is contained in:
Kjeld Schouten
2023-12-21 14:59:29 +01:00
parent 2e573a79da
commit ec3a77e83a
2 changed files with 1 additions and 57 deletions
+1 -1
View File
@@ -1,7 +1,7 @@
kubeVersion: '>=1.24.0-0'
apiVersion: v2
name: csi-driver-nfs
version: 1.0.7
version: 1.0.8
appVersion: latest
description: csi-driver-nfs is a nfs CSI driver for kubernetes
home: https://truecharts.org/charts/incubator/csi-driver-nfs
@@ -1,5 +1,3 @@
backupStorageLocation: {}
backupStorageLocationList: []
image:
pullPolicy: IfNotPresent
repository: tccr.io/truecharts/alpine
@@ -11,66 +9,12 @@ operator:
portal:
open:
enabled: false
schedules: {}
schedulesList: []
service:
main:
enabled: false
ports:
main:
enabled: false
velero:
configuration:
backupStorageLocation: []
volumeSnapshotLocation: []
deployNodeAgent: true
initContainers:
- image: openebs/velero-plugin:1.9.0@sha256:f89855c12dd0a9bfd1afb9a75b051f6cb0452c4c073df9fc7fff4d7983eff341
imagePullPolicy: IfNotPresent
name: opeebs-velero-plugin
volumeMounts:
- mountPath: /target
name: plugins
- image: velero/velero-plugin-for-csi:v0.6.0@sha256:fc07d1897a65d7728543b2fae9feddad087b5e7f45f45c3adaeda2ef4996fd50
imagePullPolicy: IfNotPresent
name: velero-plugin-for-csi
volumeMounts:
- mountPath: /target
name: plugins
- image: velero/velero-plugin-for-aws:v1.8.0@sha256:466d4ee963de87b28e38098f5f91401bde514c7c2449ea6da4009be626a08f6c
imagePullPolicy: IfNotPresent
name: velero-plugin-for-aws
volumeMounts:
- mountPath: /target
name: plugins
namespace:
labels:
- key: pod-security.kubernetes.io/enforce
value: privileged
- key: pod-security.kubernetes.io/enforce-version
value: latest
- key: pod-security.kubernetes.io/audit
value: privileged
- key: pod-security.kubernetes.io/audit-version
value: latest
- key: pod-security.kubernetes.io/warn
value: privileged
- key: pod-security.kubernetes.io/warn-version
value: latest
nodeAgent:
podVolumePath: /var/lib/kubelet/pods
privileged: true
resources:
limits:
cpu: 2000m
memory: 2048Mi
resources:
limits:
cpu: 4000m
memory: 4Gi
schedules: {}
volumeSnapshotLocation: {}
volumeSnapshotLocationList: []
workload:
main:
enabled: false