ci: revert e2e Go pin to stable now that chainsaw/kuttl support Go 1.26#4488
Merged
Merged
Conversation
The e2e-k3d-chainsaw and e2e-k3d-kuttl jobs were pinned to Go 1.25.x with
a TODO noting that chainsaw/kuttl were missing the new testDeps.ModulePath
introduced by Go 1.26. Both projects have since shipped releases that
require go >= 1.26.0:
* github.com/kudobuilder/kuttl v0.26.0 -> go 1.26.0
* github.com/kyverno/chainsaw (main) -> go 1.26.0
actions/setup-go@v6 sets GOTOOLCHAIN=local when an explicit version is
requested, so the pinned 1.25.x runner cannot auto-upgrade to satisfy
those modules and the e2e jobs fail with:
go: github.com/kudobuilder/kuttl/cmd/kubectl-kuttl@latest:
github.com/kudobuilder/kuttl@v0.26.0 requires go >= 1.26.0
(running go 1.25.9; GOTOOLCHAIN=local)
Switch both e2e jobs to 'go-version: stable', matching every other Go job
in the same workflow (go-test, kubernetes-api, kubernetes-k3d,
coverage-report). This unblocks the e2e checks that have been red on main
since the Go 1.26 bump landed in CrunchyData#4479.
andrewlecuyer
approved these changes
May 14, 2026
ValClarkson
added a commit
that referenced
this pull request
May 14, 2026
The setup-go pin to 1.25.x in the e2e-k3d-kuttl job, combined with GOTOOLCHAIN=local in CI, prevented Go from auto-upgrading to 1.26 when go run-ing kuttl@latest. Recent kuttl releases require Go >= 1.26 (testDeps.ModulePath, etc.), causing both v1.30 and v1.34 e2e jobs to fail when downloading and building the kubectl-kuttl binary. Switch the job back to go-version: stable so the runner installs the current toolchain, matching what we already do on main (PR #4488). The operator binary itself is built inside Docker against the project's go directive (1.25.0), so this only affects the host toolchain used to fetch and run kuttl from source. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
The
e2e-k3d-chainsawande2e-k3d-kuttljobs were pinned to Go 1.25.x with a TODO noting that chainsaw/kuttl were missingtestDeps.ModulePath(added in Go 1.26). Both upstreams have since shipped releases that requirego >= 1.26.0:github.com/kudobuilder/kuttl@v0.26.0->go 1.26.0github.com/kyverno/chainsaw(main) ->go 1.26.0actions/setup-go@v6setsGOTOOLCHAIN=localwhen an explicit version is requested, so a 1.25 runner cannot auto-upgrade to build them.