docs: document existing ACR image deployment (#6967)#6986
Closed
sagarkt wants to merge 1 commit into
Closed
Conversation
sagarkt
requested review from
prakarsh-dt,
vikramdevtron and
vivek-devtron
as code owners
July 16, 2026 08:23
|
Bito Review Skipped - Source Branch Not Found |
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.
Description
Documents how to use an existing Azure Container Registry in both supported scenarios:
The guide covers cluster pull access,
imagePullSecrets, manual deployment behavior, and the External CI webhook request. It also corrects the existing webhook example to use the backend'sapi-tokenheader.Fixes #6967
How Has This Been Tested?
git diff --cached --checkapi-tokenheader against both backend authentication call sitesChecklist:
Does this PR introduce a user-facing change?
Documentation only; no runtime behavior changes.