You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test-connection pods do not take into account the global.image.registry setting, see here, but hardcode the download of the busybox container from the default docker repository.
Describe the enhancement/feature:
Desired outcome and acceptance tests:
Busybox container pod should be downloaded from the registry set in global.image.registry and only default to docker IO.
We will remove the pods instead as they are only needed for test purposes and we should only rely on the readiness probes moving forward! This was used to check the healthiness of the stack via a helm cmd.
hisImminence
changed the title
[ENHANCEMENT] global.image.registry should work for test-connection pods too
[ENHANCEMENT] Remove test-connection pods
Feb 24, 2025
⚠ see update
Describe the use case:
test-connection pods do not take into account the
global.image.registry
setting, see here, but hardcode the download of the busybox container from the default docker repository.Describe the enhancement/feature:
Desired outcome and acceptance tests:
Busybox container pod should be downloaded from the registry set in
global.image.registry
and only default to docker IO.Related Support cases
The text was updated successfully, but these errors were encountered: