You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When applying multiple patches to the deploy manifests via Kustomize (v5.0.3+), it fails to build with the following error:
$ kustomize build ./deploy/kubernetes/overlays/stable
Error: updating name reference in'spec/template/spec/containers/envFrom/configMapRef/name' field of 'Deployment.v1.apps/ebs-csi-controller.kube-system': considering field 'spec/template/spec/containers/envFrom/configMapRef/name' of object Deployment.v1.apps/ebs-csi-controller.kube-system: visit traversal on path: [envFrom configMapRef name]: expected sequence or mapping node
It expects the spec/template/spec/containers/envFrom field to be a sequence or mapping node, however, it's null.
/kind bug
What happened?
When applying multiple patches to the deploy manifests via Kustomize (v5.0.3+), it fails to build with the following error:
It expects the
spec/template/spec/containers/envFrom
field to be a sequence or mapping node, however, it's null.aws-ebs-csi-driver/deploy/kubernetes/base/controller.yaml
Line 97 in ed3c33d
What you expected to happen?
I expected both patches to be applied.
How to reproduce it (as minimally and precisely as possible)?
Add the following patches to the deploy/kubernetes/overlays/stable/kustomization.yaml:
Then run:
Anything else we need to know?
This problem can be solved by avoiding generating empty
envFrom
fields from the Helm charts.aws-ebs-csi-driver/deploy/kubernetes/base/controller.yaml
Line 97 in ed3c33d
Environment
kubectl version
): N/AThe text was updated successfully, but these errors were encountered: