fix: managed identity not being enabled for nodes #220
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.
Fixes #197
Description
We currently hardcode managed identity enablement for AKS node bootstrapping script to be
false
, which is incorrect as we need it to betrue
per our managed identity support. This PR is a quick fix for this. See the linked issue for a consequence of this bug.How was this change tested?
acrpull
role to the kubelet identity and compare the results before and after the fix. This role assignment should be equivalent toattach-acr
.Does this change impact docs?
Release Note