How does the Bitnami kubectl deprecation affect ITRS Analytics deployments?

This FAQ provides guidance on migrating from the deprecated bitnami/kubectl image to supported alternatives to prevent deployment issues in ITRS Analytics online installations.

Important

ITRS Analytics versions prior to 2.15.4 will fail to deploy on online installations due to bitnami/kubectl image deprecation. Air-gapped deployments are unaffected. To prevent deployment failures, you must upgrade to version 2.15.4 or later. This release includes updates that replace bitnami/kubectl with chainguard/kubectl

Instances running ITRS Analytics 2.12.0+1 or later (up to 2.15.x) can upgrade directly to version 2.15.4. This is the recommended upgrade path. For instances running versions earlier than 2.12.0+1, the workaround must still be applied prior to upgrading. Version 2.12.0+1 is a required release in the upgrade sequence, and skipping it may result in encountering the issue.

What is happening with the bitnami/kubectl image? Copied

Bitnami announced that all images in their public catalog will be migrated to a legacy repository on September 2025. After this date, images can no longer be retrieved via docker.io/bitnami. This means the bitnami/kubectl image will no longer be accessible through the standard Docker Hub registry path.

See the official Bitnami announcement for details.

Why does this affect my deployments? Copied

If your deployments, Kubernetes manifests, or ITRS Analytics packages reference bitnami/kubectl images, they will fail to pull the image. This affects:

How does this affect ITRS Analytics packages? Copied

ITRS Analytics utilizes kubectl/bitnami images as part of packages prior to version 2.15.4. This creates critical issues:

Which versions are affected?

What should I do if I’m using an affected version? Copied

  1. Immediate action:

    • Audit your current deployments to identify bitnami/kubectl usage.
    • Plan migration to ITRS Analytics version 2.15.4 or later.
    • There may be required intermediate releases before 2.15.4 depending on your current version. Please contact ITRS Support to determine the proper upgrade path for your specific deployment.

  2. For new deployments:

    • Do not install any ITRS Analytics version below 2.15.4 - these versions will fail due to the deprecated bitnami/kubectl dependency.
    • We strongly recommend making it a standard rule for fresh installations to always use version 2.15.4 or later.
    • Ensure your package manifests reference chainguard/kubectl or approved alternatives.

How to work around online deployment limitations before ITRS Analytics 2.15.4? Copied

If you need to install ITRS Analytics online deployments that don’t come with the Chainguard image, you can use the following workaround procedure. This allows you to install older versions of ITRS Analytics by redirecting the deprecated bitnami/kubectl image to a supported alternative.

Note

Workaround applicability and notes:

  • Works for both new installations and upgrades.
  • Only needs to be done once; remains effective for future upgrades.
  • During upgrades, you may need to:
    • Delete the job.
    • Redeploy the instance to apply image redirection.

This is a temporary workaround and should only be used until you can upgrade to ITRS Analytics version 2.15.4 or later.

Installing ITRS Analytics on BYO online deployments Copied

Prerequisites Copied

  1. Install the latest release of Gatekeeper.

    kubectl apply -f https://raw.githubusercontent.com/open-policy-agent/gatekeeper/v3.20.1/deploy/gatekeeper.yaml

    For detailed installation instructions, refer to Gatekeeper’s documentation.

  2. Download and apply the assignImage.yaml manifest file:

    kubectl apply -f assignImage.yaml

    This manifest will redirect bitnami/kubectl image references to the supported alternative.

  3. Apply this patch to ensure the manifest does not interfere with upgrades.

    kubectl patch -p '{"spec":{"minAvailable":0}}' -n gatekeeper-system pdb/gatekeeper-controller-manager

  4. Deploy ITRS Analytics.

    Proceed with your normal deployment process. The image redirection will ensure that any references to the deprecated bitnami/kubectl image will be automatically redirected to the supported alternative.

  5. If you have already upgraded to the version 2.15.4 after installing Gatekeeper, you can safely uninstall it by running the following commands:

    kubectl delete -f assignImage.yaml
kubectl delete -f https://raw.githubusercontent.com/open-policy-agent/gatekeeper/v3.20.1/deploy/gatekeeper.yaml

Installing ITRS Analytics on Embedded Cluster online deployments Copied

Prerequisites Copied

Perform these steps after the cluster becomes available and before deploying ITRS Analytics through the KOTS Admin console.

  1. Start a shell with access to the itrs-analytics cluster.

    sudo ./itrs-analytics shell

  2. Pull the bitnamilegacy/kubectl image and tag it so that bitnami/kubectl references point to the bitnamilegacy/kubectl path.

    k0s ctr image pull docker.io/bitnamilegacy/kubectl:1.29.4
k0s ctr image tag docker.io/bitnamilegacy/kubectl:1.29.4 docker.io/bitnami/kubectl:1.29.4
k0s ctr image pull docker.io/bitnamilegacy/kubectl:1.32.2
k0s ctr image tag docker.io/bitnamilegacy/kubectl:1.32.2 docker.io/bitnami/kubectl:1.32.2

    Note

    You don’t need to delete these images manually, as the container runtime will automatically remove them once a certain threshold is reached.
["ITRS Analytics"] ["FAQ"]

Was this topic helpful?