Kubebuilder has been building those artifacts binaries to allow users
to use the ENV TEST functionality provided by controller-runtime
for several years. However, Google Cloud Platform has deprecated the Container Registry ,
which has been used to build and promote these binaries tarballs.
Additionally, ongoing changes and the phase-out of the previous GCP infrastructure mean
that Kubebuilder maintainers are no longer able to build or ensure the promotion of these binaries.
Therefore, since those have been building to allow the controller-runtime
ENV TEST library to work, it has been started to be built by controller-runtime itself
under the controller-gen releases page . From controller-runtime
release v0.19.0 the binaries will begin to be pulled out from this page instead.
For more information, see the PR that introduces this change here .
Kubebuilder publishes test binaries and container images in addition
to the main binary releases.
You can find test binary tarballs for all Kubernetes versions and host platforms at https://go.kubebuilder.io/test-tools.
You can find a test binary tarball for a particular Kubernetes version and host platform at https://go.kubebuilder.io/test-tools/${version}/${os}/${arch}.
To know more about the tooling used to configure ENVTEST which is used in the setup-envtest target in the Makefile
of the projects build with Kubebuilder see the [README][readme]
of its tooling.
