Skip to content

ci: revert e2e-k3d-kuttl Go pin to stable on REL_5_8#4490

Merged
ValClarkson merged 1 commit into
CrunchyData:REL_5_8from
ValClarkson:ci/e2e-kuttl-stable-rel-5-8
May 14, 2026
Merged

ci: revert e2e-k3d-kuttl Go pin to stable on REL_5_8#4490
ValClarkson merged 1 commit into
CrunchyData:REL_5_8from
ValClarkson:ci/e2e-kuttl-stable-rel-5-8

Conversation

@ValClarkson
Copy link
Copy Markdown
Contributor

The e2e-k3d-kuttl job on REL_5_8 is pinned to go-version: '1.25.x' with a TODO about kuttl not yet supporting Go 1.26. Combined with GOTOOLCHAIN=local, this prevents Go from auto-upgrading when building kuttl@latest (v0.26.0), which requires Go >= 1.26 (testDeps.ModulePath).
This is the cause of the persistent e2e-k3d-kuttl (v1.30) and e2e-k3d-kuttl (v1.34) failures on every recent PR targeting REL_5_8.
Mirrors PR #4488 (which fixed the same issue on main) by switching the job back to go-version: stable.

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 CrunchyData#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>
@ValClarkson ValClarkson requested a review from andrewlecuyer May 14, 2026 15:08
@ValClarkson ValClarkson merged commit 6a2bea8 into CrunchyData:REL_5_8 May 14, 2026
17 of 18 checks passed
@ValClarkson ValClarkson deleted the ci/e2e-kuttl-stable-rel-5-8 branch May 14, 2026 15:29
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.

2 participants