Default helm install fails on chart version 2.0.0

[vishal-chdhry]

Describe the bug
v2.0.0 chart added a dependency on secrets-store-csi-driver: 4048ba1, this causes default install to fail because both of the charts install a daemonset with same name .Chart.Name by default

To Reproduce

Steps to reproduce the behavior:

❯ helm install secrets-store-csi-driver-provider-aws secrets-store-csi-driver-provider-aws --namespace kube-system --create-namespace --repo https://aws.github.io/secrets-store-csi-driver-provider-aws --wait
Error: INSTALLATION FAILED: 1 error occurred:
        * daemonsets.apps "secrets-store-csi-driver-provider-aws" already exists

Do you also notice this bug when using a different secrets store provider (Vault/Azure/GCP...)? No

If yes, the issue is likely with the k8s Secrets Store CSI driver, not the AWS provider. Open an issue in that repo.

Expected behavior

The install should work

Environment:
OS, Go version, etc.

Additional context
Add any other context about the problem here.

[simonmarty]

Version 2.0.0 of the Helm chart includes the Secrets Store CSI Driver as a Helm dependency. If you'd like to restore the previous behavior, pass --set secrets-store-csi-driver.install=false when installing the ASCP Helm chart.

See the README and release notes for more info.

[vishal-chdhry]

@simonmarty helm installation throws an error with secret-store-csi-driver enabled

[vishal-chdhry]

I ran the following command on an empty kind cluster, and it fails

helm install secrets-store-csi-driver-provider-aws secrets-store-csi-driver-provider-aws --namespace kube-system --create-namespace --repo https://aws.github.io/secrets-store-csi-driver-provider-aws --wait

[simonmarty]

How is your kind cluster reaching the EKS control plane? Are you using EKS Anywhere?

Our provider needs to talk to EKS (either through IRSA or pod identities) to get AWS credentials. We've tested version 2.0.0 of the Helm chart on an EKS cluster with both secrets-store-csi-driver.install=true and false (after installing the CSI Driver helm chart), it deployed without issues.

[vishal-chdhry]

How is your kind cluster reaching the EKS control plane?

I am using kind cluster as an example to provide reproducible steps, this error is related to helm chart and it is a name conflict issue. I think the cluster type only comes into picture once the installation is done, since the failure happens before it, it wont affect it. I am seeing the exact same error across cluster types

I would suggest updating the Daemonset's name to avoid conflict

[simonmarty]

Default (secrets-store-csi-driver.install=true)

❯ helm repo list
NAME                           URL
secrets-store-csi-driver        https://kubernetes-sigs.github.io/secrets-store-csi-driver/charts
aws-secrets-manager             https://aws.github.io/secrets-store-csi-driver-provider-aws
❯ helm install -n kube-system sscdpa aws-secrets-manager/secrets-store-csi-driver-provider-aws
NAME: sscdpa
LAST DEPLOYED: Fri Jul 25 21:30:49 2025
NAMESPACE: kube-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
❯ kubectl get pods -n kube-system
NAME                                                 READY   STATUS    RESTARTS   AGE
aws-node-6fvtn                                       2/2     Running   0          35d
aws-node-8sqzp                                       2/2     Running   0          35d
aws-node-txcn8                                       2/2     Running   0          35d
coredns-5449774944-887lp                             1/1     Running   0          35d
coredns-5449774944-lcm65                             1/1     Running   0          35d
eks-pod-identity-agent-5q8x7                         1/1     Running   0          35d
eks-pod-identity-agent-mtp9q                         1/1     Running   0          35d
eks-pod-identity-agent-n87qh                         1/1     Running   0          35d
kube-proxy-j7xff                                     1/1     Running   0          35d
kube-proxy-p5sjr                                     1/1     Running   0          35d
kube-proxy-w2lqn                                     1/1     Running   0          35d
metrics-server-8b674cb55-59fh4                       1/1     Running   0          35d
metrics-server-8b674cb55-q5qfl                       1/1     Running   0          35d
sscdpa-secrets-store-csi-driver-5j6pc                3/3     Running   0          9s
sscdpa-secrets-store-csi-driver-gnbmv                3/3     Running   0          9s
sscdpa-secrets-store-csi-driver-kmr96                3/3     Running   0          9s
sscdpa-secrets-store-csi-driver-provider-aws-6wdm8   1/1     Running   0          9s
sscdpa-secrets-store-csi-driver-provider-aws-lm8hd   1/1     Running   0          9s
sscdpa-secrets-store-csi-driver-provider-aws-wc52v   1/1     Running   0          9s

With secrets-store-csi-driver.install=false

❯ helm repo list
NAME                           URL
secrets-store-csi-driver        https://kubernetes-sigs.github.io/secrets-store-csi-driver/charts
aws-secrets-manager             https://aws.github.io/secrets-store-csi-driver-provider-aws
❯ helm install -n kube-system sscd secrets-store-csi-driver/secrets-store-csi-driver
NAME: sscd
LAST DEPLOYED: Fri Jul 25 21:27:39 2025
NAMESPACE: kube-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
The Secrets Store CSI Driver is getting deployed to your cluster.

To verify that Secrets Store CSI Driver has started, run:

  kubectl --namespace=kube-system get pods -l "app=secrets-store-csi-driver"

Now you can follow these steps https://secrets-store-csi-driver.sigs.k8s.io/getting-started/usage.html
to create a SecretProviderClass resource, and a deployment using the SecretProviderClass.
❯ helm install -n kube-system sscdpa aws-secrets-manager/secrets-store-csi-driver-provider-aws --set secrets-store-csi-driver.install=false
NAME: sscdpa
LAST DEPLOYED: Fri Jul 25 21:28:13 2025
NAMESPACE: kube-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
❯ kubectl get pods -n kube-system
NAME                                                 READY   STATUS    RESTARTS   AGE
aws-node-6fvtn                                       2/2     Running   0          35d
aws-node-8sqzp                                       2/2     Running   0          35d
aws-node-txcn8                                       2/2     Running   0          35d
coredns-5449774944-887lp                             1/1     Running   0          35d
coredns-5449774944-lcm65                             1/1     Running   0          35d
eks-pod-identity-agent-5q8x7                         1/1     Running   0          35d
eks-pod-identity-agent-mtp9q                         1/1     Running   0          35d
eks-pod-identity-agent-n87qh                         1/1     Running   0          35d
kube-proxy-j7xff                                     1/1     Running   0          35d
kube-proxy-p5sjr                                     1/1     Running   0          35d
kube-proxy-w2lqn                                     1/1     Running   0          35d
metrics-server-8b674cb55-59fh4                       1/1     Running   0          35d
metrics-server-8b674cb55-q5qfl                       1/1     Running   0          35d
sscd-secrets-store-csi-driver-786sq                  3/3     Running   0          37s
sscd-secrets-store-csi-driver-9xtnz                  3/3     Running   0          37s
sscd-secrets-store-csi-driver-tqsmn                  3/3     Running   0          37s
sscdpa-secrets-store-csi-driver-provider-aws-qsbhr   1/1     Running   0          8s
sscdpa-secrets-store-csi-driver-provider-aws-s9pb7   1/1     Running   0          9s
sscdpa-secrets-store-csi-driver-provider-aws-sfbgh   1/1     Running   0          8s

[simonmarty]

Ok, I'm finally caught up to your issue. Sorry it took so long. Your issue is specific to the command you are running (specifically the name you are doing your Helm installation under). I am able to reproduce it.

❯ helm install secrets-store-csi-driver-provider-aws secrets-store-csi-driver-provider-aws --namespace kube-system --create-namespace --repo https://aws.github.io/secrets-store-csi-driver-provider-aws --wait
Error: INSTALLATION FAILED: 1 error occurred:
        * daemonsets.apps "secrets-store-csi-driver-provider-aws" already exists

[janek64]

I am facing the same error message, but I think it is not exclusively related to the specific name @simonmarty has mentioned. Instead, it seems like it occurs when my Helm release name is too long and the name of the DaemonSet gets truncated:

helm install myapp-dev-myapplication-eks-cluster-ascp secrets-store-csi-driver-provider-aws --namespace kube-system --repo https://aws.github.io/secrets-store-csi-driver-provider-aws --set secrets-store-csi-driver.syncSecret.enabled=true --set secrets-store-csi-driver.install=true --wait
Error: INSTALLATION FAILED: 1 error occurred:
        * daemonsets.apps "myapp-dev-myapplication-eks-cluster-ascp-secrets-store-csi-driv" already exists