What steps did you take and what happened:
Using the Helm Chart 7.0.0 of velero we could not set the imagePullSecrets on service account due to a error
similar to
# serviceaccounts "velero" was not valid:
# * patch: Invalid value: "map[metadata:map[imagePullSecrets:[map[name:acr-pull-secret]]]]": strict decoding error: unknown field "metadata.imagePullSecrets"
What steps did you take and what happened: Using the Helm Chart 7.0.0 of velero we could not set the imagePullSecrets on service account due to a error
similar to
What did you expect to happen:
the https://github.com/vmware-tanzu/helm-charts/blob/velero-7.0.0/charts/velero/templates/serviceaccount-server.yaml#L20-L23 instead
should be
Anything else you would like to add: Kubernetes guidelines about serviceaccount https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-image-pull-secret-to-service-account
Seems be a small issue but its impacts on data mover as it uses the same image of velero, but there is no configuration for imagePullSecrets to it. https://github.com/vmware-tanzu/velero/blob/v1.14.0/pkg/exposer/image.go#L45-L46
Environment:
helm version:
helm chart version and app version (use
helm list -n <YOUR NAMESPACE>
):Kubernetes version:
Kubernetes installer & version: (not needed)
Cloud provider or hardware configuration: (not needed)
OS (e.g. from
/etc/os-release
): (not needed)