Skip to content
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.

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

[ENHANCEMENT] Remove test-connection pods #2984

Closed
hisImminence opened this issue Feb 24, 2025 · 3 comments
Closed

[ENHANCEMENT] Remove test-connection pods #2984

hisImminence opened this issue Feb 24, 2025 · 3 comments
Assignees
Labels
kind/enhancement New feature or request

Comments

@hisImminence
Copy link
Contributor

hisImminence commented 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

@hisImminence hisImminence added kind/enhancement New feature or request support Marks an issue as related to a customer support request (don't edit the lable) labels Feb 24, 2025
@hisImminence
Copy link
Contributor Author

ETA: latest June release

@hisImminence hisImminence added the good first issue Good for newcomers label Feb 24, 2025
@hisImminence
Copy link
Contributor Author

hisImminence commented Feb 24, 2025

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 hisImminence changed the title [ENHANCEMENT] global.image.registry should work for test-connection pods too [ENHANCEMENT] Remove test-connection pods Feb 24, 2025
@hisImminence hisImminence removed good first issue Good for newcomers support Marks an issue as related to a customer support request (don't edit the lable) labels Feb 24, 2025
@hisImminence hisImminence self-assigned this Feb 25, 2025
@hisImminence
Copy link
Contributor Author

PR merged: #3001

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant