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

Changing/set the location for aks_uai_name #378

Open
1 task done
tdu29f opened this issue Apr 11, 2024 · 1 comment
Open
1 task done

Changing/set the location for aks_uai_name #378

tdu29f opened this issue Apr 11, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@tdu29f
Copy link

tdu29f commented Apr 11, 2024

Is your feature request related to a problem? Please describe.

We are using the script with "BYO" options and private cluster. Network resources are provided by Azure admins in a separate Resource Group (<vnet_resource_group_name>) and the cluster is deployed into existing VNET with existing Subnets and Route Table. The issue is that the managed identity for aks needs contributor permissions on (some of) those objects.
When we use the <aks_uai_name>, the identity is supposed to be located in the VNET Resource Group. As this Resource Group should only contain networking resources we cannot create it there upfront.

Describe the solution you'd like

A possible solution could be to tell the script to look for the managed identity in the other Resource group, set by the <resource_group_name> variable.
Actually this is also where it is being created when <aks_uai_name> is not used.

Describe alternatives you've considered

Alternative is to create the identity in upfront in the <vnet_resource_group_name>
But it is against guidelines from the client.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@tdu29f tdu29f added enhancement New feature or request new Added to an issue when it's new ;) labels Apr 11, 2024
@riragh
Copy link
Member

riragh commented May 3, 2024

Thank you for opening this feature enhancement request. This request will be reviewed and internal ticket will be created if the request is approved. I'll post updates to this issue.

@riragh riragh removed the new Added to an issue when it's new ;) label May 3, 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
Projects
None yet
Development

No branches or pull requests

2 participants