Update aks-secure-baseline add-ons (V1 and V2) to support aks cluster with user assigned identity #238
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.
Description
aks-secure-baseline add-on doesn't work when using an user-assigned identity (user-msi)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The principal id value cannot be null when you do a role assignment. This value needs to be fetched from managed identity and used while doing the role assignment using the user msi.
Screenshots
Does this introduce a breaking change
Testing
Testing done with an aks cluster created with user assigned identity. Sample tfvars snippet below:
237