-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fix Velero tests and stop using bitnami images #21274
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
Conversation
The following files, which will be shipped with the agent, were modified in this PR and You can ignore this if you are sure the changes in this PR do not require QA. Otherwise, consider removing the label. List of modified files that will be shipped with the agent
|
Codecov Report❌ Patch coverage is Additional details and impacted files🚀 New features to boost your workflow:
|
It took ages for the test to finish and eventually it failed. But it can run properly locally. I will keep looking into this on Monday. |
Review from Kyle-Neale is dismissed. Related teams and files:
- agent-integrations
- velero/tests/conftest.py
* Move bitnami image used for testing to bitnami legacy * Add changelog * Increase timeout when installing velero * Decrease timeout for installation. Did not work. * Add custom kubectl image (cherry picked from commit 04d89ef)
* Move bitnami image used for testing to bitnami legacy * Add changelog * Increase timeout when installing velero * Decrease timeout for installation. Did not work. * Add custom kubectl image (cherry picked from commit 04d89ef) Co-authored-by: Juanpe Araque <[email protected]> Co-authored-by: Steven Yuen <[email protected]>
What does this PR do?
Modify the repo used by the velero helm chart from the bitnami one to bitnami legacy. This is not a final solution but VMware Tanzu is still discussing a final alternative to the bitnami image.
EDIT: we started using the legacy repo but that created issues on the test setup. The helm chart was timing out in CI, not when running locally. Since the only reason we are using the
bitnami/kubectl
image is because the helmchart uses some utilities other than kubectl, the final fix is create our own debian image withkubectl
in it.See: vmware-tanzu/helm-charts#698
Motivation
Do not rely on bitnami images for testing.
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged