Skip to content

connectedk8s: release v1.11.5 - #10475

Open
Ashlee Nanze (ashnanze) wants to merge 9 commits into
Azure:mainfrom
AzureArcForKubernetes:release/v1.11.5
Open

Ashlee Nanze (ashnanze) wants to merge 9 commits into
Azure:mainfrom
AzureArcForKubernetes:release/v1.11.5

Conversation

@ashnanze

@ashnanze Ashlee Nanze (ashnanze) commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

🤖 PR Validation — ️✔️ All clear

Breaking Changes Suppressions
️✔️ None ️✔️ None

Summary

Hotfix release of the connectedk8s extension version 1.11.5.

Changes

  • Update the cluster prediagnostics image to 1.38.0 to handle endpoint redirects in strict outbound allowlist and AGC scenarios.
  • Retry transient pre-onboarding diagnostic pod-log retrieval failures.
  • Continue onboarding when logs remain unavailable after retries and the diagnostic job completed successfully.
  • Continue onboarding when stale diagnostic Helm release cleanup fails while retaining warning and telemetry reporting.
  • Treat a single generic DNS timeout as transient while keeping repeated or confirmed failures blocking.
  • Support both extracted Helm chart directories and packaged .tgz charts.
  • Add AGC diagnostic chart compatibility for USSec and USNat using scheme-less MCR repository values.
  • Update the extension version and release history to 1.11.5.

Includes fixes from AzureArcForKubernetes#106, AzureArcForKubernetes#109, AzureArcForKubernetes#110, and AzureArcForKubernetes#111.

Validation

  • 513 unit tests passed.
  • Focused precheck and utility suites: 196 tests passed.
  • Wheel built successfully with version 1.11.5.
  • All changed files are under src/connectedk8s/.
  • Partner Validated

* Retry transient prediagnostic log retrieval failures

* Continue onboarding when diagnostic logs remain unavailable
Copilot AI balanced review requested due to automatic review settings October 15, 2026 19:03
@microsoft-github-policy-service microsoft-github-policy-service Bot added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Oct 15, 2026
@microsoft-github-policy-service

Copy link
Copy Markdown
Contributor

Thank you for your contribution Ashlee Nanze (@ashnanze)! We will review the pull request and get back to you soon.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 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 ""
@yonzhan

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 2 pipeline(s).

@ashnanze
Ashlee Nanze (ashnanze) marked this pull request as draft October 20, 2026 23:35
junw98 and others added 6 commits October 21, 2026 09:31
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
@ashnanze
Ashlee Nanze (ashnanze) marked this pull request as ready for review October 23, 2026 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Auto-Assign Auto assign by bot Connected Kubernetes customer-reported Issues that are reported by GitHub users external to the Azure organization.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants