Skip to content

Migrate to registry.k8s.io #35777

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Migrate to registry.k8s.io #35777

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dd2cbf0
migrate to registry.k8s.io
Babbili Oct 25, 2025
cb938e7
fix images tags
Babbili Oct 25, 2025
5484226
migrate to registry.k8s.io
Babbili Oct 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion config/jobs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Some good examples include:
- [pull-release-notes-lint] uses `node:11` to run `npm ci && npm lint`
- [pull-org-test-all] uses `launcher.gcr.io/google/bazel:0.26.0` to run `bazel test //...`

Many jobs use `gcr.io/k8s-testimages/foo` images that are built from source in
Many jobs use `registry.k8s.io/foo` images that are built from source in
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many of our CI jobs use staging images, which is an exception to the general guidance to use production published images. These images are not published because they're not intended for external re-use, they're internal to the project.

However, this should point to the community owned project

[`images/`]. Some of these have evolved organically, with way more dependencies
than needed, and will be periodically bumped by PRs. These are sources of
technical debt that are often not very well maintained. Use at your own risk,
Expand Down
2 changes: 1 addition & 1 deletion config/jobs/kubernetes/repo-infra/repo-infra-presubmits.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ presubmits:
preset-bazel-scratch-dir: "true"
spec:
containers:
- image: gcr.io/k8s-testimages/launcher.gcr.io/google/bazel:latest-kubernetes-master
- image: registry.k8s.io/launcher.gcr.io/google/bazel:latest-kubernetes-master
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simple substitution like this does not work, this image does not exist.

Please confirm that these images exist.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cpanato it kinda looks like we could archive this repo and turn down the CI jobs, no commits since January 2022 ...

Copy link
Author

@Babbili Babbili Oct 29, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you're right, i'd push the images that doesn't exist yet, please which project, artifact repo and region, i don't have access to the GCP projects, will i need a serviceaccount key instead or creating a prow job will do it. i found this maybe helpful

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't an image we built, it was copied from launcher.gcr.io/google/bazel, we should avoid building yet another image ourselves, working with the owners of github.com/kubernetes/repo-infra to find a solution.

Perhaps the bazel parts of this repo can be deleted and this replaced with a kubekins-e2e job running make.

We do not have any humans pushing images directly. See https://github.com/kubernetes/registry.k8s.io?tab=readme-ov-file#registryk8sio

command:
- ./presubmit.sh
imagePullPolicy: Always
Expand Down
2 changes: 1 addition & 1 deletion config/jobs/kubernetes/test-infra/test-infra-presubmits.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ presubmits:
preset-service-account: "true"
spec:
containers:
- image: gcr.io/k8s-testimages/gubernator:v20230111-cd1b3caf9c
- image: registry.k8s.io/gubernator:latest
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this image does not exist.

command:
- ./gubernator/test-gubernator.sh
env:
Expand Down
2 changes: 1 addition & 1 deletion config/prow/autobump-config/prow-job-autobump-config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ extraFiles:
targetVersion: "latest"
prefixes:
- name: "k8s-testimages images"
prefix: "gcr.io/k8s-testimages/"
prefix: "registry.k8s.io/"
repo: "https://github.com/kubernetes/test-infra"
summarise: false
consistentImages: false
Expand Down
2 changes: 1 addition & 1 deletion experiment/pod.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ metadata:
spec:
containers:
- name: k8s-e2e-test
image: gcr.io/k8s-testimages/kubekins-e2e-prow:v20170929-9413e407
image: registry.k8s.io/kubekins-e2e-prow:latest
args:
- "--timeout=60"
env:
Expand Down
4 changes: 2 additions & 2 deletions images/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Images

Each subdirectory corresponds to an image that is automatically built and pushed to gcr.io/k8s-testimages when PRs that touch them merge using [postsubmit prowjobs](https://testgrid.k8s.io/sig-testing-image-pushes) that run the [image-builder](/images/builder)
Each subdirectory corresponds to an image that is automatically built and pushed to registry.k8s.io/ when PRs that touch them merge using [postsubmit prowjobs](https://testgrid.k8s.io/sig-testing-image-pushes) that run the [image-builder](/images/builder)

## Updating test-infra images

Expand Down Expand Up @@ -39,7 +39,7 @@ There is no automated testing pipeline for images:

1. Merge a PR changing something in the image directory.

1. Grep the [prowjob configs](/config/jobs) to find out which jobs are using `gcr.io/k8s-testimages/<image-name>:latest` and monitor [TestGrid](http://testgrid.k8s.io) for new failures corresponding to your change.
1. Grep the [prowjob configs](/config/jobs) to find out which jobs are using `registry.k8s.io/<image-name>:latest` and monitor [TestGrid](http://testgrid.k8s.io) for new failures corresponding to your change.

* On failure, send a new PR to rollback your last one or a fix if you know immediately.
* Some of these images might be presubmits; you could monitor them at http://prow.k8s.io
Expand Down
2 changes: 1 addition & 1 deletion logexporter/cluster/logexporter-daemonset.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ spec:
spec:
containers:
- name: logexporter-test
image: gcr.io/k8s-testimages/logexporter:v20220831-a9d3b0ad39
image: registry.k8s.io/logexporter:latest
env:
- name: NODE_NAME
valueFrom:
Expand Down
2 changes: 1 addition & 1 deletion logexporter/cluster/logexporter-pod.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ metadata:
spec:
containers:
- name: logexporter-test
image: gcr.io/k8s-testimages/logexporter:v0.1.6
image: registry.k8s.io/logexporter:v0.1.6
env:
- name: NODE_NAME
valueFrom:
Expand Down