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
I am able to setup CSI driver for windows EKS worker node by setting up value, windows.enabled=true.
I can see a daemonset for CSI secrets driver on both Windows EKS worker nodes.
But same is not true for AWS Provider https://aws.github.io/secrets-store-csi-driver-provider-aws/
On this page AWS has not mentioned if provider is available to run on Windows worker nodes.
I can see with default deployment daemonset of secrets-store-csi-driver-provider-aws is only running on Linux worker node of EKS.
Kindly note ours is a multi OS EKS cluster, we have Linux as well as Windows Worker nodes.
Pods scheduled on Windows Worker nodes need to use secrets/parameters stored in AWS Secrets Manager or AWS SSM parameter Store.
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
-
Hello All,
I am able to setup CSI driver for windows EKS worker node by setting up value, windows.enabled=true.
I can see a daemonset for CSI secrets driver on both Windows EKS worker nodes.
But same is not true for AWS Provider
https://aws.github.io/secrets-store-csi-driver-provider-aws/
On this page AWS has not mentioned if provider is available to run on Windows worker nodes.
I can see with default deployment daemonset of secrets-store-csi-driver-provider-aws is only running on Linux worker node of EKS.
Kindly note ours is a multi OS EKS cluster, we have Linux as well as Windows Worker nodes.
Pods scheduled on Windows Worker nodes need to use secrets/parameters stored in AWS Secrets Manager or AWS SSM parameter Store.
Any help regarding the same is appreciated
Beta Was this translation helpful? Give feedback.
All reactions