Secret CSI AWS Provider not working on Node with Taint.

[comicrr]

What steps did you take and what happened:

I am using the AWS Provider in SecretProviderClass to create secrets for my pods.

• In Environment A, the nodes have no taints.
• In Environment B, the nodes have the following taint: node.kubernetes.io/dedicated-for-load-test=true.
• In Environment A, everything works perfectly.
• In Environment B, the Secret CSI pods display the error: Failed to fetch secret from all regions: arn:aws:secretsmanager::㊙️-.

Initially, I thought the Secret CSI pods were not scheduled due to the taint. However, they were successfully spawned on each tainted node:

• csi-secrets-store-provider-aws-stvgz
• secrets-store-csi-driver-qf5pb

What did you expect to happen:

The Secret CSI should work even on nodes with taints.

Which provider are you using:

• AWS Provider

Environment:

• Secrets Store CSI Driver version: (use the image tag):
  • csi-secrets-store-provider-aws-stvgz : public.ecr.aws/aws-secrets-manager/secrets-store-csi-driver-provider-aws:1.0.r2-35-g41dc61e-2022.12.16.20.38
  • secrets-store-csi-driver-qf5pb : registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.8.0
• Kubernetes version: (use kubectl version):
  • Client = v1.27.8
  • Server = v1.28.9-eks-036c24b