doc: deprecate AzureStorageIdentityObjectID field #1456
Merged
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.
What type of PR is this?
/kind documentation
What this PR does / why we need it:
doc: deprecate AzureStorageIdentityObjectID field
from blobfuse 2.3.0, AzureStorageIdentityObjectID relies on azure cli installed on the node, pls use
AzureStorageIdentityClientID or
AzureStorageIdentityResourceID parameter instead.
CX needed to install Azure CLI on worker nodes manually.
With this PR, ObjectID (Managed Identity Authentication) now relies on the azure cli.
Azure/azure-storage-fuse@644728f#diff-b7b39483e2bf51ebe17ba7827a1b18cbaf75b74fcfe0796ae7a2d3e667b45289R95
Every time CX reimages a worker node with nodeOSimage Upgrade, the Azure CLI needs to be installed manually.
To avoid having to install Azure CLI on worker nodes, user should use AzureStorageIdentityClientID or AzureStorageIdentityResourceID instead of AzureStorageIdentityObjectID
Which issue(s) this PR fixes:
Fixes #
Requirements:
Special notes for your reviewer:
Release note: