Repository navigation
chore: Backport/upstream 20261118 - #1394
Merged
Wei Weng (weng271190436) merged 14 commits intoNov 19, 2026
Merged
Wei Weng (weng271190436) merged 14 commits into
Wei Weng (weng271190436) merged 14 commits into
Conversation
* 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>
…ts to reduce flakiness (Azure#1050)
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>
Codecov Report❌ Patch coverage is
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. 🚀 New features to boost your workflow:
|
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 of your changes
Backport all upstream changes since the cutoff included in #1386, through kubefleet-dev/kubefleet commit
31156aca6884b73e6374de23f99195e7eaf1419b(2026-11-18).e0826660feat: add selected-resource authorization for CRP (feat: add selected-resource authorization for CRP kubefleet-dev/kubefleet#990)576f55d1fix: address Trivy CVEs for 2026-W46 (fix: address Trivy CVEs for 2026-W46 kubefleet-dev/kubefleet#1042)a5302a52docs: point the unavailablePeriodSeconds doc link at kubefleet.dev (docs: point the unavailablePeriodSeconds doc link at kubefleet.dev kubefleet-dev/kubefleet#1040)46ae3d04test: use longer timeout when cleaning up namespaces in account of GC delays (test: use longer timeout when cleaning up namespaces in account of GC delays kubefleet-dev/kubefleet#1051)de34b683test: adjust the cost diff threshold in property provider related tests to reduce flakiness (test: adjust the cost diff threshold in property provider related tests to reduce flakiness kubefleet-dev/kubefleet#1050)c34934d9chore: bump oss/go/microsoft/golang from 1.26.10-1 to 1.26.11-1 in /docker (chore: bump oss/go/microsoft/golang from 1.26.10-1 to 1.26.11-1 in /docker kubefleet-dev/kubefleet#1048)2ff195aachore: bump step-security/harden-runner from 2.22.3 to 2.22.4 (chore: bump step-security/harden-runner from 2.22.3 to 2.22.4 kubefleet-dev/kubefleet#1047)1a2da976chore: bump docker/login-action from 4.7.0 to 4.8.0 (chore: bump docker/login-action from 4.7.0 to 4.8.0 kubefleet-dev/kubefleet#1046)86353a87chore: bump azure/setup-helm from 5.0.1 to 5.1.0 (chore: bump azure/setup-helm from 5.0.1 to 5.1.0 kubefleet-dev/kubefleet#1045)dfc21635chore: bump the codeql-action group across 1 directory with 3 updates (chore: bump the codeql-action group across 1 directory with 3 updates kubefleet-dev/kubefleet#933)31156acachore: bump the all-others group across 1 directory with 5 updates (chore: bump the all-others group across 1 directory with 5 updates kubefleet-dev/kubefleet#1043)I have:
make reviewableto 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/validatorpassed.make reviewablepassed 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.Special notes for your reviewer
go.goms.io/fleetmodule path and adapted the new CRP authorizer files accordingly.GOEXPERIMENT=systemcryptofor 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.1.26.11-1.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.