🚨 Action Required: Ensure that you no longer use https://storage.googleapis.com/kubebuilder-tools

[camilamacedo86]

⚠️ IMPORTANT ⚠️

Artifacts provided under https://storage.googleapis.com/kubebuilder-tools are deprecated and Kubebuilder maintainers are no longer able to support, build, or ensure the promotion of these artifacts.

You will find the ENVTEST binaries available in the new location from k8s release 1.28, see: https://github.com/kubernetes-sigs/controller-tools/blob/main/envtest-releases.yaml. Also, binaries to test your controllers after k8s 1.29.3 will no longer be found in the old location. New binaries are only promoted in the new location.

The artefacts for ENVTEST k8s 1.31 are exclusively available at: Controller Tools Releases. You should ensure that your projects are using the new location. Please ensure you use setup-envtest from the controller-runtime release v0.19.0 to be able to download those. This update is fully transparent for Kubebuilder users assuming that they properly update their scaffolds to use setup-envtest from controller-runtime branch release-0.19.

You can refer to the Makefile of the Kubebuilder scaffold and observe that the envtest setup is consistently aligned across all controller-runtime releases. Starting from release-0.19, it is configured to automatically download the artefact from the correct location, ensuring that kubebuilder users are not impacted.

# To know the available versions check: 
# - https://github.com/kubernetes-sigs/controller-tools/blob/main/envtest-releases.yaml
ENVTEST_K8S_VERSION = 1.31.0
# Controller-Runtime branch `release-0.19` has the implementation of the setup-envtest's code responsible
# for downloading the tarball from the correct location.
ENVTEST_VERSION ?= release-0.19
...
.PHONY: envtest
envtest: $(ENVTEST) ## Download setup-envtest locally if necessary.
$(ENVTEST): $(LOCALBIN)
	$(call go-install-tool,$(ENVTEST),sigs.k8s.io/controller-runtime/tools/setup-envtest,$(ENVTEST_VERSION))

❓ Why is this happening?

Kubebuilder has been producing these artifacts for several years. However, due to recent infrastructure changes for projects under the Kubernetes umbrella, we now require the use of shared infrastructure. Since these artefacts use projects/binaries from projects that are not under the SIG org more info, we unfortunately cannot build and promote these artifacts using the new Kubernetes infrastructure. Additionally, since these artefacts are only useful for the controller-runtime ENVTEST library, it makes more sense for them to be maintained under the controller-runtime maintainers' domain.

Additionally, ongoing changes and the phase-out of the previous GCP infrastructure mean that Kubebuilder maintainers are no longer able to support, build, or ensure the promotion of these images. (More info)

Please ensure that you update your configurations accordingly to avoid any disruptions. If you have any questions or need further assistance, feel free to ask in this discussion thread and/or kubebuilder slack channel.