Repository navigation
connectedk8s: release v1.11.5 - #10475
Open
Ashlee Nanze (ashnanze) wants to merge 9 commits into
Open
Ashlee Nanze (ashnanze) wants to merge 9 commits into
Ashlee Nanze (ashnanze) wants to merge 9 commits into
Conversation
* Retry transient prediagnostic log retrieval failures * Continue onboarding when diagnostic logs remain unavailable
microsoft-github-policy-service
Bot
requested review from
Yu Chen (jsntcy) and
Yong Zhang (yonzhan)
October 15, 2026 19:03
Contributor
|
Thank you for your contribution Ashlee Nanze (@ashnanze)! We will review the pull request and get back to you soon. |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Exhausted log retries incorrectly cause unverified diagnostic results to be reported as successful prechecks.
1 open finding
What changed in this PR
Releases connectedk8s 1.11.5 to reduce onboarding failures caused by transient diagnostic log retrieval errors.
Changes:
- Adds bounded retries and a warning-based fallback when logs remain unavailable.
- Adds tests for retry recovery, exhaustion, and permanent errors.
- Updates the extension version and release history.
| File | Description |
|---|---|
| src/connectedk8s/setup.py | Bumps version to 1.11.5. |
| src/connectedk8s/HISTORY.rst | Documents the hotfix. |
| src/connectedk8s/azext_connectedk8s/tests/unittests/test_precheckutils.py | Tests log retrieval retry behavior. |
| src/connectedk8s/azext_connectedk8s/_precheckutils.py | Adds retries and unavailable-log fallback. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| "prediagnostics-log-retrieval-unavailable", | ||
| message, | ||
| ) | ||
| return "" |
Collaborator
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
Ashlee Nanze (ashnanze)
marked this pull request as draft
October 20, 2026 23:35
Co-authored-by: Ashlee Nanze <ashleenanzework@gmail.com>
* Fix connectedk8s onboarding diagnostic regressions * Fix connectedk8s unit test pipeline path * Limit onboarding fixes to incident rows 2 4 and 8
Removing non-blocking set_user_fault calls is enough to keep successful connect commands reporting Success. Drop mark_command_succeeded so the extension does not depend on Azure CLI's private telemetry session. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: aea35d0f-7a31-424d-8478-08a6f8df5b7c
Ashlee Nanze (ashnanze)
marked this pull request as ready for review
October 23, 2026 19:15
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.

🤖 PR Validation — ️✔️ All clear
Summary
Hotfix release of the connectedk8s extension version 1.11.5.
Changes
.tgzcharts.Includes fixes from AzureArcForKubernetes#106, AzureArcForKubernetes#109, AzureArcForKubernetes#110, and AzureArcForKubernetes#111.
Validation
src/connectedk8s/.