Helm template for controller-poddisruptionbudget.yaml does not honor --namespace setting

[charlieoleary]

/kind bug

What happened?

I installed the latest version of the Helm chart into a custom namespace. The ebs-csi-controller-pod-disruption-budget was created in the kube-system namespace instead of the namespace I specified.

What you expected to happen?

I expected all resources to be created in the specified namespace.

How to reproduce it (as minimally and precisely as possible)?

1. Install the Helm chart into a custom namespace:

helm upgrade --install aws-ebs-csi-driver \
    --namespace my-custom-namespace \
    --create-namespace \
    aws-ebs-csi-driver/aws-ebs-csi-driver

2. Confirm that all resources have been installed in the custom namespace:

kubectl get all -n my-custom-namespace

3. Confirm that the PodDisruptionBudget has been installed in the kube-system namespace:

kubectl get poddisruptionbudget -n kube-system

Anything else we need to know?:

Environment

• Kubernetes version (use kubectl version): N/A
• Driver version: Helm Chart v1.0.0

[vdhanan]

/assign

[vdhanan]

hoping to release a new helm chart with this fix today

[charlieoleary]

Thanks for jumping on this so quickly.