kubekins-e2e is the primary image used in CI by most prowjobs. It has many useful utilities installed, listed here and available at gcr.io/k8s-staging-test-infra/kubekins-e2e.
In 2024, we rolled out a new version kubekins-e2e called kubekins-e2e-v2 available at us-central1-docker.pkg.dev/k8s-staging-test-infra/images/kubekins-e2e and it has many benefits:
- multiarch support
- removed various test-infra dependencies
- removed bazel and other CI legacy kruft
- simplified build step, its built directly from upstream debian instead of a sig-testing intermediate image
kubekins-e2e v1 build steps => upstream debian -> bootstrap -> kubekins-e2e
kubekins-e2e v2 build steps => upstream debian -> kubekins-e2e
bootstrap.py has been removed for years now in #30846
We want maintainers and contributors to switch to the new image as soon as possible. You can switch to this image if the following is true:
- You are not using the scenarios script, aka
/workspace/scenarios/kubernetes_e2e.py
- You are not relying on tools such as logexporter, etc that are in test-infra.
Early in January, we'll amend the unit tests to block the addition of new jobs that use the old image
kubekins-e2e is the primary image used in CI by most prowjobs. It has many useful utilities installed, listed here and available at
gcr.io/k8s-staging-test-infra/kubekins-e2e.In 2024, we rolled out a new version kubekins-e2e called kubekins-e2e-v2 available at
us-central1-docker.pkg.dev/k8s-staging-test-infra/images/kubekins-e2eand it has many benefits:kubekins-e2e v1 build steps =>
upstream debian -> bootstrap -> kubekins-e2ekubekins-e2e v2 build steps =>
upstream debian -> kubekins-e2ebootstrap.py has been removed for years now in #30846
We want maintainers and contributors to switch to the new image as soon as possible. You can switch to this image if the following is true:
/workspace/scenarios/kubernetes_e2e.pyEarly in January, we'll amend the unit tests to block the addition of new jobs that use the old image