-
Notifications
You must be signed in to change notification settings - Fork 168
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
Allow the usage/creation of a User Managed Identity for AKS kubelet identity #551
Comments
I'd like to work on this one. @Gordonby we might need a discussion on the design part. I will reach out to you separately. |
Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month. |
Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month. |
I'll help pick this up. Initial thoughts
@iamvighnesh would you still like to work on this as well? |
**Problem description
AKS supports multiple user managed identities, one of which is the kubelet identity.
A Kubelet identity enables access granted to the existing identity prior to cluster creation. This feature enables scenarios such as connection to ACR with a pre-created managed identity.
In this scenario AKS is going to use the User Managed Identity created prior to cluster setup in order to do ACR operations permitted with that specific identity.
**Solution description
As a user I would like to either be able to provide a User Managed Identity to the cluster setup process with necessary rights on ACR or have one created and assigned for me with the ability to choose the ACR rights to be assigned to the identity.
**Alternatives
As the documentation describes if the cluster is not created with a managed kubelet identity the user cannot assign one :
The text was updated successfully, but these errors were encountered: