📖Golang 1.24+ in setup-envtest/README.md

[erichorwath]

It seems that with 9d65299 Go 1.24+ is required for latest envtest.

This PR would help to quickly fix pipeline errors like: https://github.com/SAP/cf-service-operator/actions/runs/14042277233/job/39315277162

test -s /workspace/bin/setup-envtest || GOBIN=/workspace/bin go install sigs.k8s.io/controller-runtime/tools/setup-envtest@latest
go: downloading sigs.k8s.io/controller-runtime v0.20.4
go: downloading sigs.k8s.io/controller-runtime/tools/setup-envtest v0.0.0-20250324134234-561fa39c550f
go: sigs.k8s.io/controller-runtime/tools/setup-envtest@latest: sigs.k8s.io/controller-runtime/tools/[email protected] requires go >= 1.24.0 (running go 1.23.0; GOTOOLCHAIN=local)

@sbueringer jfyi

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: erichorwath / name: Eric Horwath (4a8fd51, 8f1aca8, f0807fe)

[k8s-ci-robot]

Welcome @erichorwath!

It looks like this is your first PR to kubernetes-sigs/controller-runtime 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/controller-runtime has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @erichorwath. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[sbueringer]

Thx!

In general I probably wouldn't use latest setup-envtest in pipelines. It's not like setup-envtest is changing a lot so latest would be required :)

To give you some additional alternatives to compiling setup-envtest yourself:

• we provide setup-envtest binaries via GitHub release attachments on all controller-runtime releases
• with the next CR minor version you can use envtest to download the binaries you need for tests: ✨ envtest: add option to download binaries, bump envtest to v1.32.0 #3135
  • So depending on your use case you might not need setup-envtest anymore

(cc @camilamacedo86 in case the above is interesting for kubebuilder as well)

/lgtm
/approve
/ok-to-test

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: f74bbef22402bf4c455171df956b562a3fe4deb3

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: erichorwath, sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment