-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubelet Credential Provider Support #2310
Comments
thanks for bringing this up, we'll take a look at it. |
Status update on this work... I think I have most things in place with #2377, but having some trouble validating things. I've verified with the team that it looks like all the right configuration is in place, but things are not working as expected. The current theory is there is some conflict between our use of the in-tree AWS cloud provider and this newer functionality that may actually need the out-of-tree cloud provider. Still working on trying to validate that assumption. Since there is still a bit of work to do here, it doesn't look like this will make it into the 1.10.0 release. Retargeting this to 1.11.0 and will update as we find out more. |
This support has merged, but I wanted to point out the final implementation is slightly different than what was originally requested in this issue. Please take a look at the current settings in the |
What I'd like:
Allow credential-provider settings to be passed into a credential helper. In this case I would like to use IAM Roles Anywhere with ecr-credential-provider. For this particular case it would require an api setting
These values would get piped down into a configuration file for kubelet credential provider.
If this setting is enabled the feature gate in #1702 could just be enabled for the kubelet, as those are needed for kubelet-credential-provider.
The text was updated successfully, but these errors were encountered: