# ACTION REQUIRED: Percona Everest and Bitnami Container Catalog Changes ⚠️ **URL:** \ **Category:** Percona Everest\ **Created:** [September 19, 2025, 10:00am UTC](https://forums.percona.com/t/action-required-percona-everest-and-bitnami-container-catalog-changes/39419 "2025-09-19T10:00:44Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Diogo\_Recharte](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/diogo_recharte/32/8004_2.png) [@Diogo\_Recharte](https://forums.percona.com/u/Diogo_Recharte)\ **Post date:** [September 19, 2025, 10:00am UTC](https://forums.percona.com/t/action-required-percona-everest-and-bitnami-container-catalog-changes/39419/1 "2025-09-19T10:00:44Z")
**Attention Percona Everest Users:** Bitnami is restructuring its container catalog on **September 29, 2025**. To ensure your Percona Everest operations remain seamless, you must take a few proactive steps now. ## Mandatory Fix to Prevent Future Issues ✅ To avoid installation and uninstallation failures, every Percona Everest user must perform the following actions. The `everestctl` CLI caches old chart versions, which can cause issues even after upgrading Everest. By clearing the cache and, if necessary, upgrading your charts, you will ensure all future operations are safe. 1. **Clear the `everestctl` cache.** This step is **mandatory for all users** , regardless of your Everest version. The `everestctl` CLI caches chart information. To ensure it uses the new image references for all future operations, you must clear this cache. ### If you are on Percona Everest v1.8.1 or earlier: You must manually update your Helm charts to use the new image. **If you are on v1.9.0 or later, you can skip these steps.** 1. **List all installed Everest charts.** Find all Helm releases for both the `everest` and `everest-db-namespace` charts. Note the **release name** , **namespace** , and **`APP VERSION`** for each one. 2. **Upgrade the main Everest chart.** Upgrade the `everest` chart (e.g., `everest-system`) using its specific details. 3. **Upgrade the database namespace charts.** Repeat the `helm upgrade` command for each `everest-db-namespace` chart you found in step 1. 4. **Restart Everest Operator.** You’re all set! By following these steps, you’ve ensured your Percona Everest deployment is resilient to the Bitnami container catalog changes. * * * ## What’s Changing with Bitnami? 💥 Bitnami has announced it is [restructuring its container catalog](https://github.com/bitnami/containers/issues/83267) and moving most container images to a legacy repository on **September 29, 2025**. After this date, any installations, updates, or uninstallations that rely on the old image references will fail. **Percona Everest** is affected because it depends on the `bitnami/kubectl` image for several critical tasks: - The `everest-operators-installer` job during installation and namespace provisioning. - Cleanup jobs like `pre-delete`, `csv-cleanup`, and `psp-cleanup` during uninstallation. This means that after **September 29, 2025** , your Everest deployments could become stuck if you try to perform these operations. * * * ## Troubleshooting (If You’re Already Stuck After Sept 29) 🛠 If you find yourself with a failed operation after the Bitnami change takes effect, use these steps to resolve the issue. ### Scenario 1: Installation or Namespace Provisioning Is Stuck Your `everestctl install`, `everestctl namespaces add`, or `everestctl namespaces update` command is stalled, showing a status like this: ```bash ℹ️ Installing Everest version 1.8.1 ✅ Installing Everest Helm chart ✅ Ensuring Everest API deployment is ready ✅ Ensuring Everest operator deployment is ready ✅ Ensuring OLM components are ready ✅ Ensuring monitoring stack is ready ∙∙● Provisioning database namespace 'everest' Esc/Ctrl+c quit ``` #### Step-by-Step Fix 1. **Open a new terminal** and leave the stalled process running. 2. **Verify the stuck Helm release.** Confirm the `everest-db-namespace` chart is in a `pending-install` state. Note the **release name** and **namespace** from the output. In this example, it’s `everest` in the `everest` namespace. 3. **Confirm the cause.** Check the pod status to ensure the problem is an `ImagePullBackOff` for the `bitnami/kubectl:latest` image. 4. **Delete the stuck job.** 5. **Check that the install continues.** The original `everestctl` command should now proceed. Note the **`APP VERSION`** of your Helm release, as you’ll need it in the next step. 6. **Upgrade the Helm release.** Use the release name, namespace, and `APP VERSION` from the previous steps to upgrade the chart. 7. **Restart Everest Operator.** 8. Your immediate issue is now resolved. Remember to complete the steps in the **Mandatory Fix to Prevent Future Issues** section if you haven’t already, to avoid this problem in the future. * * * ### Scenario 2: Uninstallation Is Stuck Your `everestctl uninstall` command is stalled while deleting a namespace: ```bash ✅ Deleting database clusters in namespace 'everest' ✅ Deleting backup storages in namespace 'everest' ✅ Deleting monitoring instances in namespace 'everest' ●∙∙ Deleting database namespace 'everest' Esc/Ctrl+c quit ``` #### Step-by-Step Fix 1. **Open a new terminal** and leave the stalled process running. 2. **Verify the stuck Helm release.** Confirm the `everest-db-namespace` chart is in an `uninstalling` state. Note the **release name** and **namespace**. 3. **Identify the stuck job.** List the jobs in the namespace and find the one with a `Running` status. Note the **job’s name**. 4. **Confirm the cause.** Check the pod to ensure it’s an `ImagePullBackOff` for the `bitnami/kubectl:latest` image. Note the **pod’s name** and **container name**. 5. **Patch the pod.** Replace the `bitnami/kubectl` image with the new `percona/everest-helmtools:0.0.1` image. **Make sure to replace the pod and container names with your own.** 6. **Repeat as needed.** The uninstallation should now progress, but it might get stuck again on other cleanup jobs like `psp-cleanup`. Repeat steps 3-5, identifying and patching any new stuck jobs until the uninstallation completes. 7. Your immediate issue is now resolved. Remember to complete the steps in the **Mandatory Fix to Prevent Future Issues** section if you haven’t already, to avoid this problem in the future.