Replies: 1 comment 3 replies
-
Feel free to share a link to the fork if it's open-source so we can take a look. Most of the difficulty in us distributing official support for Windows is having the tooling to continuously verify that changes we introduce to this provider won't break Windows customers. Without good support from EKS, this is difficult for us. I'm going to move this to a discussion. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We utilize dozens of EKS clusters and have lots of secrets to mount on windows nodes/containers. EKS support for windows is not something that is short-term according to the EKS team and is not in an early stage.
We expect to be able to use secrets with our windows containers in EKS and to be able to use them with secrets store csi driver.
We have looked at this before and we did fork this project to support windows, the support only requires a couple of small adjustments (filepath separator and explicitly closing some file AFAIR). We are happy to create a PR to do the adjustments for the helm chart, docker builds, and go code.
We have been using this fork for almost 2 years and it just works. However, we don't want to be managing this as we think this needs to be supported by AWS since they are standing behind windows support and since it's not a lot of work.
Beta Was this translation helpful? Give feedback.
All reactions