Skip to main content

Illumio Advisories

Bitnami Repository Changes

Bitnami is implementing a significant change to its container image distribution model, effective August 28, 2025.

As a result of this change, the Bitnami etcd image used in the Illumio Container CLAS Storage will be migrating.

Who is Impacted

Customers with CLAS enabled who use the default Helm chart values from quay.io Illumio Kubernetes Operator or pull images directly from the public Bitnami Docker repository.

Who is Not Impacted

  • Customers with CLAS deployments that pull images from a private repository.

  • Customers running the product in a Legacy (Non-CLAS) deployment.

Impact

  • If you do not take any action before the repository migration, any restart of the Illumio storage pod will fail. This will result in policy update failures in your Kubernetes and OpenShift clusters.

  • If the repository is not updated, existing CLAS deployments will continue to run but will fail when the storage pod is restarted and rescheduled on a different Kubernetes node.

Required Action

Important

To ensure uninterrupted operation of your applications and Illumio policy in your clusters, you must update your Helm chart yaml values file before August 28, 2025.

Instructions to update the etcd Repository for CLAS Deployment

  1. Add or update the following section of your helm chart values file:

    storage:
      registry: "docker.io/bitnamilegacy"
  2. Get the current version of the helm chart:

    helm list --namespace illumio-system
  3. Use the same version of the helm upgrade:

    helm upgrade illumio -f illumio-values.yaml oci://quay.io/illumio/illumio --namespace illumio-system --version VERSION_FROM_ABOVE
  4. Confirm that the storage pod is running:

    kubectl get pod --namespace illumio-system
  5. Confirm that the etcd image repo is updated:

    kubectl get statefulset --namespace illumio-system illumio-storage --output yaml|grep image:
  6. Confirm that etcd is initialized. One of the last few lines of the storage pod log will say successfully notified init daemon:

    kubectl logs --namespace illumio-system statefulset/illumio-storage
  7. Confirm that kubelink has restarted and is running:

    kubectl get pod --namespace illumio-system
  8. Confirm that kubelink policy fetches and updates:

    kubectl logs --namespace illumio-system deployment/illumio-kubelink
  9. Confirm the etcd database size:

    kubectl exec --namespace illumio-system illumio-storage-0 -- etcdctl endpoint status --write-out=table

Recommendation

To ensure continuity and uninterrupted service, Illumio recommends that you review and consider upgrading to the new 5.6 version of the Illumio Kubernetes Operator.