Don't create cilium-azure secret when azure.clientID is not set #40269
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using Azure workload identity (the AKS-recommended authentication method), it is the AWI mutating admission webhook that injects client id, tenant id and so on into pods. If cilium-operator's pod spec already has the environment variable
AZURE_CLIENT_ID
mounted from the secret, the webhook does not overwrite it with the correct value, workload identity credential fails to acquire a token, and cilium-operator cannot sync IPAM information. And if neither client id nor client secret are specified, there is no need to create the cilium-azure secret.This commit modifies the cilium helm chart to skip creating the cilium-azure secret and the environment variable bindings to it in cilium-operator's pod spec when
azure.clientID
helm value is not set.