Skip to content
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

Open
naioja opened this issue Mar 17, 2023 · 5 comments
Open
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers Keep Open needs-discussion An issue that needs a discussion with core maintainers to agree how to move forward

Comments

@naioja
Copy link
Contributor

naioja commented Mar 17, 2023

**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 :

@Gordonby Gordonby added enhancement New feature or request good first issue Good for newcomers labels Mar 20, 2023
@iamvighnesh
Copy link
Contributor

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.

@github-actions
Copy link
Contributor

Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month.

@github-actions github-actions bot added the stale An issue that hasn't had a lot of love recently label Apr 29, 2023
@iamvighnesh iamvighnesh removed the stale An issue that hasn't had a lot of love recently label May 1, 2023
@github-actions
Copy link
Contributor

Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month.

@github-actions github-actions bot added the stale An issue that hasn't had a lot of love recently label May 31, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 30, 2023
@JimPaine JimPaine reopened this Sep 4, 2023
@JimPaine
Copy link
Contributor

JimPaine commented Sep 4, 2023

I'll help pick this up.

Initial thoughts

  • Ability to bring your own UAI
  • Create UAI if not supplied
  • Must meet prereqs i.e. rbac enabled and user assigned identity for control plane
  • Work with existing UAI for control plane work
  • Handle role assignment requirement between the two identities

@iamvighnesh would you still like to work on this as well?

@JimPaine JimPaine self-assigned this Sep 4, 2023
@github-actions github-actions bot added Keep Open and removed stale An issue that hasn't had a lot of love recently labels Sep 5, 2023
@deepdolphin
Copy link
Contributor

@deepdolphin deepdolphin added the needs-discussion An issue that needs a discussion with core maintainers to agree how to move forward label Feb 6, 2024
@iamvighnesh iamvighnesh removed their assignment Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers Keep Open needs-discussion An issue that needs a discussion with core maintainers to agree how to move forward
Projects
None yet
Development

No branches or pull requests

5 participants