A RetroSearch Logo

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

Search Query:

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

Ability to get list of overridable registries in e2e.test · Issue #96475 · kubernetes/kubernetes · GitHub

What would you like to be added:

A way to list known YAML keys to override registries with KUBE_TEST_REPO_LIST without having to look inside the code.

Why is this needed:

To run conformance test on airgapped cluster, users need to prepare for the images being used by conformance test suite in registries which are accessible by their cluster. From what I have gathered, the workflow today is:

  1. Look at the code mentioned above (RegistryList struct)
  2. Write override YAML based on the keys listed
  3. Pass the YAML as KUBE_TEST_REPO_LIST

My desired workflow would be:

  1. Run ./e2e.test -list-registries
  2. Save the output above into a file & modify as needed
  3. Pass the file as KUBE_TEST_REPO_LIST

Which would help me automate things and be aware whenever registries consumed by the test suite changes.

Possible outcome:

❯ ./e2e.test -list-registries
buildImageRegistry: k8s.gcr.io/build-image
dockerGluster: docker.io/gluster
dockerLibraryRegistry: docker.io/library
e2eRegistry: gcr.io/kubernetes-e2e-test-images
e2eVolumeRegistry: gcr.io/kubernetes-e2e-test-images/volume
gcRegistry: k8s.gcr.io
promoterE2eRegistry: k8s.gcr.io/e2e-test-images
sigStorageRegistry: k8s.gcr.io/sig-storage

Notes:

I'm using -list-registries as a placeholder for the feature, definitely open to be discussed

/kind feature
/sig testing

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