Request Feature: Startup Taint #454
Description
Hello, requesting a feature in regards to startup taints:
Problem:
We are running into issues with pods starting before secrets-store-csi driver is ready.
How it would work:
Administrators should be able to add a startup taint to the nodes. Something like secrets.csi.aws.com/agent-not-ready:NoExecute.
Once secrets-store-csi-driver is started, it would remove this taint from the node.
aws-efs-csi-driver has this feature:
https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/ee80ddde4e2c8886131c2081e425dc105f222214/docs/README.md?plain=1#L186-L189
Current workaround:
Workarounds is adding init containers to pods that verify the health of secrets provider before attempting to start... or just having readiness/liveness probe thresholds tuned so the service will keep retrying until CSI driver is ready, but this is not an elegant approach to the situation.
Thank you for considering my request, and please let me know if there is any other workarounds to the problen I am facing.