NLB-6626: Add documentation for dataplane managed identity#1748
Draft
rnandwal-f5 wants to merge 3 commits intomainfrom
Draft
NLB-6626: Add documentation for dataplane managed identity#1748rnandwal-f5 wants to merge 3 commits intomainfrom
rnandwal-f5 wants to merge 3 commits intomainfrom
Conversation
Add quickstart guide explaining how to use managed identity from NGINXaaS dataplane to access Azure resources via IMDS. Includes: - Overview of MI support on dataplane - Sample njs script to fetch tokens and query blob storage - Security considerations for IMDS endpoint exposure
… identity Update quickstart to state that managed identity access from dataplane only works with system-assigned identities, and reference managed identity docs for legacy deployment details.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This MR adds a quickstart guide for using managed identity (MI) from the NGINXaaS dataplane to access Azure resources via the Instance Metadata Service (IMDS).
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩