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 that run the image-builder
There is no automated testing pipeline for images:
- Any jobs that use the
:latest
tag use the latest published image immediately - Any jobs that use a
:v{date}-{sha}[-{variant}]
tag (e.g.:v20200407-c818676-master
) are updated to use the latest published image ~daily. This is accomplished by PR's created by the autobumper prowjob, which are merged by test-infra oncall once a day during weekdays.
-
Merge a PR changing something in the image directory.
-
Grep the prowjob configs to find out which jobs are using
gcr.io/k8s-testimages/<image-name>:latest
and monitor TestGrid 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
-
You are done. If more breaks happen later, test-infra oncall will take care of it.