-
Notifications
You must be signed in to change notification settings - Fork 188
testing: update bitnami image to bitnamilegacy #9645
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
base: main
Are you sure you want to change the base?
Conversation
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
cc72116
to
c45abb4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we consider alternatives? The bitnami/kubectl
is only used as opentelemetry-kube-stack helm chart testdata so I don't think it's needed that we stick to a bitnami image.
What about something like https://hub.docker.com/r/rancher/kubectl or some other kubectl image ?
Fair point. From what I could read in the announcement, the bitnamilegacy images will not receive any updates, it is basically a public archive. Agree we should seek alternatives if possible. I'll try with the rancher/kubectl image. |
Okay, I misinterpreted how the testdata charts work. We download the opentelemetry-helm-charts to testdata as part of a mage step. This needs to be fixed upstream first via open-telemetry/opentelemetry-helm-charts#1768. |
|
What does this PR do?
Bitnami announced that their public image catalog will be deleted on September 29th. Migrate to an alternative image.
https://community.broadcom.com/tanzu/blogs/beltran-rueda-borrego/2025/08/18/how-to-prepare-for-the-bitnami-changes-coming-soon
Checklist
./changelog/fragments
using the changelog tool