doc(azure): shows how to use userAssignedIdentityID with clientId in azure.json

[thesse1]

Adding userAssignedIdentityID with clientId of the kubelet identity in azure.json solves the problem with multiple parallel node pool identities - issue #4132

Description

Documentation update: Adding userAssignedIdentityID with clientId of the kubelet identity in azure.json

Fixes #4132

Checklist

• Unit tests updated - not applicable, no code change
• End user documentation updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: thesse1 / name: Thomas Hesse (df122b0)

[k8s-ci-robot]

Welcome @thesse1!

It looks like this is your first PR to kubernetes-sigs/external-dns 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/external-dns has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @thesse1. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mloiseleur]

@weisdd any comment on top of this update of your PR ?

[mloiseleur]

/retitle doc(azure): shows how to use userAssignedIdentityID with clientId in azure.json

[thesse1]

@mloiseleur Thanks for reviewing this so quickly. I am fine with the change.

[weisdd]

@weisdd any comment on top of this update of your PR ?

@mloiseleur I'm a bit surprised to see anyone care about Pod-Managed Identity ("Managed identity using AKS Kubelet identity" relies on it) as it's already deprecated:

"The open source Microsoft Entra pod-managed identity (preview) in Azure Kubernetes Service has been deprecated as of 10/24/2022, and the project will be archived in Sept. 2023" (Docs).

As for your question, my PR (#3906) covered a slightly different functionality called Workload Identity, which came to replace Pod-Managed Identity, so I don't have much to add here :)

[mloiseleur]

@weisdd Thanks. That was my understanding, but I was unsure.

@thesse1 Wdyt about re-working this PR to put this identification method in a deprecated section of doc ?

[thesse1]

@mloiseleur @weisdd This change is about Managed identity using AKS Kubelet identity which is not deprecated (as far as I know). It just does not work (100%) without the userAssignedIdentityID in azure.json. Without that, it only works fine if the Kubelet identity happens to be the only user-assigned managed identity on the node pool(s).

I know that Service Principal would be more secure, but I do not have access to an SP in my AD (Entra ID).

The approach of using Managed identity using AAD Pod Identities is indeed deprecated as far as I know.

And Managed identity using Workload Identity is also not available for me.

Thanks for looking into this so closely!

Merry Christmas!

Regards,
Thomas

[weisdd]

@thesse1 Sorry, my bad, authentication using kubelet identity is still supported, just not recommended (Microsoft steers everyone towards Workload Identity).

[mloiseleur]

Then I guess we are good to go, then.
/lgtm

[Raffo]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Raffo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Raffo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment