Change the bitnami registry to bitnamilegacy

[shmsr]

Proposed commit message

Please note that this is temporary fix. See this comment and https://community.broadcom.com/tanzu/blogs/beltran-rueda-borrego/2025/08/18/how-to-prepare-for-the-bitnami-changes-coming-soon.

Ultimately, we could move to another registry and maintain the images we require if we find something suitable; otherwise, we can opt for the paid ones.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

[Copilot]

Pull Request Overview

This PR updates Docker image references from the bitnami registry to bitnamilegacy as a temporary fix in response to Bitnami registry changes. This change ensures that existing Docker-based deployments continue to function while a longer-term solution is evaluated.

• Changed base image references from bitnami/ to bitnamilegacy/ in Dockerfiles
• Affects two packages: php_fpm and etcd

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/php_fpm/_dev/deploy/docker/files/Dockerfile	Updated FROM statement to use bitnamilegacy registry for PHP-FPM image
packages/etcd/_dev/deploy/docker/Dockerfile	Updated FROM statement to use bitnamilegacy registry for etcd image

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: c7437d9

History

• 💚 Build #34055 succeeded ceaaaaf

cc @shmsr