capi: isolate Azure CI CLI auth per SIG build - #2086
Merged
kubernetes-prow[bot] merged 2 commits intoJul 3, 2026
Merged
Conversation
Contributor
|
Skipping CI for Draft Pull Request. |
kubernetes-prow
Bot
added
the
do-not-merge/work-in-progress
kubernetes-prow
Bot
added
the
size/S
This was referenced Jun 28, 2026
kubernetes-prow
Bot
added
the
cncf-cla: yes
MaxRink
force-pushed
the
tcaas/azure-ci-isolate-cli-config
branch
2 times, most recently
from
July 1, 2026 17:58
91fba2a to
8382607
Compare
MaxRink
marked this pull request as ready for review
July 3, 2026 11:08
kubernetes-prow
Bot
removed
the
do-not-merge/work-in-progress
MaxRink
force-pushed
the
tcaas/azure-ci-isolate-cli-config
branch
from
July 3, 2026 11:15
08d47f5 to
0e22fc7
Compare
kubernetes-prow
Bot
added
the
lgtm
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mboersma The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubernetes-prow
Bot
added
the
approved
vomba
pushed a commit
to elastisys/image-builder
that referenced
this pull request
Jul 14, 2026
…solate-cli-config capi: isolate Azure CI CLI auth per SIG build
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
2 participants
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 this does
The Azure SIG presubmit starts many SIG builds in the background. Today all children share the same Azure CLI config directory while Packer is using Azure CLI auth, which can leave a child without a visible default subscription.
This gives each background SIG build its own
AZURE_CONFIG_DIR, logs in inside that child, and keeps the selected Azure location scoped to that child. The parent still logs in once for shared setup such as Flatcar version discovery and cleanup.Why
This addresses an Azure SIG CI race observed while maintaining the open image-builder PR train. A target failed immediately after
init-sig.shhad successfully created the resource group/gallery:The same target succeeded in another PR, which points at a CI auth race rather than a target-specific build regression.
Validation
bash -n images/capi/scripts/ci-azure-e2e.shgit diff --checkshellcheck images/capi/scripts/ci-azure-e2e.shstill reports pre-existing findings frommain; the unquoted array expansion errors and the changedwaitPID handling are fixed by this PR.NO_COLOR=1 make lintfails locally on unrelated pre-existing Ansiblevar-naming[no-role-prefix]violations underimages/capi/ansible/; no changed shell-script syntax failure was reported.