From 97fe2abe69de7b787321e55666816c21427c5341 Mon Sep 17 00:00:00 2001 From: Chris Werner Rau Date: Mon, 16 Oct 2023 12:01:32 +0200 Subject: [PATCH 1/2] fix(velero): remove useless `nodeAgent.privileged` this clashes with the field `nodeAgent.containerSecurityContext.privileged` Signed-off-by: Chris Werner Rau --- charts/velero/README.md | 4 ++++ charts/velero/templates/node-agent-daemonset.yaml | 1 - charts/velero/values.yaml | 1 - 3 files changed, 4 insertions(+), 2 deletions(-) diff --git a/charts/velero/README.md b/charts/velero/README.md index d1bc1175..7747bf7b 100644 --- a/charts/velero/README.md +++ b/charts/velero/README.md @@ -90,6 +90,10 @@ helm upgrade vmware-tanzu/velero --reuse-values --set configurati ## Upgrading +### Upgrading to 5.1.1 + +This version removes the `nodeAgent.privileged` field, you should use `nodeAgent.containerSecurityContext.privileged` instead + ### Upgrading to v1.13 The [instructions found here](https://velero.io/docs/v1.13/upgrade-to-1.13/) will assist you in upgrading from version v1.12.x to v1.13. diff --git a/charts/velero/templates/node-agent-daemonset.yaml b/charts/velero/templates/node-agent-daemonset.yaml index f5104e3d..104f9559 100644 --- a/charts/velero/templates/node-agent-daemonset.yaml +++ b/charts/velero/templates/node-agent-daemonset.yaml @@ -175,7 +175,6 @@ spec: lifecycle: {{ toYaml .Values.nodeAgent.lifecycle | nindent 12 }} {{- end }} securityContext: - privileged: {{ .Values.nodeAgent.privileged }} {{- with $containerSecurityContext }} {{- toYaml . | nindent 12 }} {{- end }} diff --git a/charts/velero/values.yaml b/charts/velero/values.yaml index 1eeeeb07..fd1c5f8b 100644 --- a/charts/velero/values.yaml +++ b/charts/velero/values.yaml @@ -518,7 +518,6 @@ deployNodeAgent: false nodeAgent: podVolumePath: /var/lib/kubelet/pods - privileged: false # Pod priority class name to use for the node-agent daemonset. Optional. priorityClassName: "" # Resource requests/limits to specify for the node-agent daemonset deployment. Optional. From f440ce2fb3dd5fdff37865e8b59426b3268708ca Mon Sep 17 00:00:00 2001 From: Chris Werner Rau Date: Fri, 27 Oct 2023 09:41:13 +0200 Subject: [PATCH 2/2] chore: release 6.0.0 with upgrading release notes Signed-off-by: Chris Werner Rau --- charts/velero/Chart.yaml | 2 +- charts/velero/README.md | 7 ++++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/charts/velero/Chart.yaml b/charts/velero/Chart.yaml index 6f5d9c31..edf74c33 100644 --- a/charts/velero/Chart.yaml +++ b/charts/velero/Chart.yaml @@ -3,7 +3,7 @@ appVersion: 1.13.0 kubeVersion: ">=1.16.0-0" description: A Helm chart for velero name: velero -version: 5.4.1 +version: 6.0.0 home: https://github.com/vmware-tanzu/velero icon: https://cdn-images-1.medium.com/max/1600/1*-9mb3AKnKdcL_QD3CMnthQ.png sources: diff --git a/charts/velero/README.md b/charts/velero/README.md index 7747bf7b..64170693 100644 --- a/charts/velero/README.md +++ b/charts/velero/README.md @@ -87,13 +87,14 @@ If a value needs to be added or changed, you may do so with the `upgrade` comman ```bash helm upgrade vmware-tanzu/velero --reuse-values --set configuration.backupStorageLocation[0].provider= ``` +## Upgrading Chart -## Upgrading - -### Upgrading to 5.1.1 +### Upgrading to 6.0.0 This version removes the `nodeAgent.privileged` field, you should use `nodeAgent.containerSecurityContext.privileged` instead +## Upgrading Velero + ### Upgrading to v1.13 The [instructions found here](https://velero.io/docs/v1.13/upgrade-to-1.13/) will assist you in upgrading from version v1.12.x to v1.13.