Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/kubernetes/kubernetes/issues/97027 below:

Migrate kubernetes e2e tests away from use of docker.io images · Issue #97027 · kubernetes/kubernetes · GitHub

Part of umbrella to migrate kubernetes e2e test images/registries to community-owned infrastructure: kubernetes/k8s.io#1458

The following docker.io images are used by 1.20 e2e tests

docker.io/gluster/glusterdynamic-provisioner:v1.0
docker.io/library/busybox:1.29
docker.io/library/httpd:2.4.38-alpine
docker.io/library/httpd:2.4.39-alpine
docker.io/library/nginx:1.14-alpine
docker.io/library/nginx:1.15-alpine
docker.io/library/perl:5.26
docker.io/library/redis:5.0.5-alpine

We should migrate them to community owned infrastructure (ref: kubernetes/sig-release#1369 for deciding how to implement a mirror registry)

We should consider doing this for release branches as well, which may use different images/tags. So these wouldn't necessarily be cherry-picks

Two possible approaches:

• change the registry in source (I would prefer eliminating the extra "docker library" registry, and consolidate to a single e2e test image registry)
• start running tests with a config that swaps out docker.io for some other registry

/sig testing
/sig release
/area release-eng
/wg k8s-infra
/milestone v1.21

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4