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
We are trying to use secrets-store-csi-driver-provider-aws in our Kubernetes cluster, which is running on Hetzner Cloud. Our goal is to fetch secrets stored in AWS Secrets Manager. However, the provider is failing to start, and we're seeing the following error in the logs:
I0311 12:18:43.361201 1 main.go:34] Starting secrets-store-csi-driver-provider-aws version 1.0.r2-80-g8244505-2025.02.10.18.44
F0311 12:18:43.459197 1 main.go:55] Failed to listen on unix socket. error: listen unix /etc/kubernetes/secrets-store-csi-providers/aws.sock: bind: permission denied
Since we rely heavily on autoscaler I can't imagine to use any "manual intervention" method each time this issue arises.
What could be the issue here? Maybe somebody has managed to successfully deploy it onto their cluster?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We are trying to use secrets-store-csi-driver-provider-aws in our Kubernetes cluster, which is running on Hetzner Cloud. Our goal is to fetch secrets stored in AWS Secrets Manager. However, the provider is failing to start, and we're seeing the following error in the logs:
Since we rely heavily on autoscaler I can't imagine to use any "manual intervention" method each time this issue arises.
What could be the issue here? Maybe somebody has managed to successfully deploy it onto their cluster?
Beta Was this translation helpful? Give feedback.
All reactions