Skip to content

chore: Backport/upstream 20261118 - #1394

Merged
Wei Weng (weng271190436) merged 14 commits into
Azure:mainfrom
weng271190436:backport/upstream-20261118
Nov 19, 2026
Merged

Wei Weng (weng271190436) merged 14 commits into
Azure:mainfrom
weng271190436:backport/upstream-20261118

Conversation

@weng271190436

@weng271190436 Wei Weng (weng271190436) commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Description of your changes

Backport all upstream changes since the cutoff included in #1386, through kubefleet-dev/kubefleet commit 31156aca6884b73e6374de23f99195e7eaf1419b (2026-11-18).

I have:

  • Run make reviewable to ensure this PR is ready for review.

How has this code been tested

  • go test -p 2 -race -timeout=10m ./pkg/utils/authorization ./pkg/utils/validator passed.
  • make reviewable passed using the existing pinned tool binaries and reduced Go parallelism. The initial attempt exhausted filesystem space; the successful retry used a task-specific shared-memory temporary directory.
  • E2E tests and container image builds were not run.

Special notes for your reviewer

  • Preserved Azure's go.goms.io/fleet module path and adapted the new CRP authorizer files accordingly.
  • Preserved Azure-specific gRPC, gateway, and generated API dependencies while taking the upstream dependency updates.
  • Preserved Azure Linux distroless runtime images and GOEXPERIMENT=systemcrypto for FIPS compatibility. The Google distroless digest update in fix: address Trivy CVEs for 2026-W46 kubefleet-dev/kubefleet#1042 is intentionally not applied to Azure's runtime images; the Go dependency updates are included.
  • Builder images are updated to Microsoft Go 1.26.11-1.
  • This sync includes merged upstream changes only, not the unmerged override authorizer in feat: add override authorizer kubefleet-dev/kubefleet#1041.

CI follow-up

The initial CI run exposed existing infrastructure failures also present on main and other PRs. This PR now raises inotify limits for the Kind E2E and compatibility jobs, installs the Ginkgo CLI from the module-pinned version, and updates the moved Squad issue URLs. Local actionlint validation passed, the module-pinned CLI reports Ginkgo 2.34.0, and all three replacement issue URLs return HTTP 200. The custom E2E suite passed after the host-limit fix. Compatibility jobs exposed the same host-limit failure, so the fix is applied there too. Final hosted CI verification is pending.

* Initial plan

* fix: upgrade golang.org/x/net to v0.62.0

Co-authored-by: britaniar <145056127+britaniar@users.noreply.github.com>

* fix: update distroless image for zlib CVEs

Co-authored-by: britaniar <145056127+britaniar@users.noreply.github.com>

* fix: address Trivy CVEs for 2026-W46

Co-authored-by: britaniar <145056127+britaniar@users.noreply.github.com>

* Apply remaining changes

Co-authored-by: britaniar <145056127+britaniar@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: britaniar <145056127+britaniar@users.noreply.github.com>
Merge kubefleet-dev/kubefleet main through 31156ac. Preserve Azure module imports, Azure-specific dependencies, and FIPS-compatible Azure Linux runtime images.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Increase host inotify capacity before creating multi-node Kind clusters, install the Ginkgo CLI from the module-pinned version, and repair moved Squad issue links.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The compatibility jobs hit the same systemd startup failure when creating the fourth Kind cluster. Apply the E2E host inotify settings before compatibility setup, and use the module-pinned Ginkgo CLI consistently.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

@michaelawyu Chen Yu (michaelawyu) 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.

LGTM ;)

@codecov

codecov Bot commented Nov 18, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 95.40230% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.97%. Comparing base (6d4af52) to head (04c2876).
⚠️ Report is 1874 commits behind head on main.

Files with missing lines Patch % Lines
...kg/utils/authorization/clusterresourceplacement.go 93.89% 4 Missing and 4 partials ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1394       +/-   ##
===========================================
+ Coverage   63.58%   82.97%   +19.38%     
===========================================
  Files          10      236      +226     
  Lines         898    25285    +24387     
===========================================
+ Hits          571    20979    +20408     
- Misses        300     3377     +3077     
- Partials       27      929      +902     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@weng271190436
Wei Weng (weng271190436) merged commit d490947 into Azure:main Nov 19, 2026
32 of 33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants