Chainguard is launching our own Helm Charts and compatible images. With this change, we are ending support for previously published "-bitnami" images. Read on for the details!
Availability and Migration start date | Migration end date |
Jul 7, 2025 | Aug 29, 2025 |
Chainguard is excited to launch Helm Charts as a new feature of the Chainguard Containers product. We have designed Helm Charts to work with our container images, simplify deployments, improve security, and guarantee long term compatibility. Until now, many customers have deployed Chainguard Containers with open source Helm Charts; this process can be difficult and require modifications to work correctly. By publishing and maintaining Chainguard Helm Charts, we can reduce much of the deployment overhead for our customers.
Chainguard is no longer able to support images previously built for compatibility with open source Helm Charts, including “-bitnami” images.
What is changing?
Chainguard will end support for all images in the catalog which are exclusively built for compatibility with open source Bitnami Helm Charts. After August 29, 2025 these images, i.e. the “-bitnami” images, will be withdrawn from the registry. Any persisting references to old images will fail.
Why is Chainguard making this change?
To deliver the highest quality, security, and long term compatibility for our customers, we are building, maintaining, and innovating on our own first-party Helm Charts in line with our mission of being the safe source for open source.
How will this affect me?
If you are using an image from the list below, you will need to migrate to a new Chainguard container and the compatible Chainguard Helm Chart. Instructions for that specific image and chart will be in the associated README. Helm Charts will be available in your private Chainguard registry, so you may need to set up authentication client-side when you run helm install.
For Helm Charts that require additional Chainguard images, you will be provisioned with those additional images at no additional cost for the remainder of your subscription term.
What do I need to do?
Please see the list of images and Helm Charts below at the end of this article.
If you are deploying images on the list, you will need to replace them with the corresponding new Chainguard image and Helm Chart by August 29, 2025 to receive continued updates and CVE remediations, including adopting the additional images required for the given Helm Chart. You may also need to authenticate to your private Chainguard registry wherever you run helm install so that you can access and deploy our Helm Charts.
FAQs
Why do I need to use the new Charts and images?
Chainguard will no longer support images previously built for compatibility with open source Helm Charts, i.e. the “-bitnami” images. In order to leverage the associated Helm Chart functionality with Chainguard images, customers will need to migrate to the Chainguard first-party Helm Chart.
Are Chainguard Helm Charts free?
They are included with your subscription to Chainguard Containers. You will receive the Helm Chart for any entitled containers at no additional cost.
What about the additional images required for the Helm Chart?
You will be provisioned all of the images required for your Helm Chart at no additional cost for the remainder of your contract.
Refer to the Customer FAQ for even more details. If you need help or have more questions, just drop us a line at support.chainguard.dev and we’ll be happy to help.
Q: Why do I need to use the new Charts and images?
A: Chainguard will no longer support images previously built for compatibility with open source Helm Charts, including “-bitnami” images. In order to leverage the associated Helm Chart functionality with Chainguard images and benefit from continuously updated and zero-CVE images, customers will need to migrate to the Chainguard first-party Helm Chart.
Q: Are Chainguard’s Helm Charts free?
A: Yes, the charts are included with your subscription to Chainguard Containers. You will receive the Helm Chart for any entitled containers at no additional cost.
Q: What about the additional images required for the Helm Chart?
A: You will be provisioned all of the images required for your Helm Chart at no additional cost for the remainder of your contract.
Q: Can I test the new images and Helm Charts today?
A: We will notify you as we release new helm charts and Chainguard Container images.
Q: How will the Helm Charts be distributed?
A: Chainguard’s Helm Charts will be distributed via OCI registry. They will be available in the same OCI registry your images are in (cgr.dev).
Q: Which images do I need to migrate?
A: Please refer to the table below. If you are deploying images from the “Previous Image Name” column, you must replace them with the corresponding new Chainguard image using the provided Helm Chart to receive continued updates and CVE remediations, including adopting the additional images required for the given Chart.
| New Helm Chart | New Image Name | Previous Image Name | Additional Notes |
|
|
|
|
1. | iamguarded-charts/elasticsearch |
|
|
|
|
|
|
|
2. | iamguarded-charts/postgresql |
|
|
|
|
|
|
|
3. | iamguarded-charts/kibana |
|
|
|
|
|
|
|
4. | iamguarded-charts/memcached |
|
|
|
|
|
|
|
5. | iamguarded-charts/rabbitmq |
|
|
|
|
|
|
|
6. | iamguarded-charts/rabbitmq-cluster-operator |
|
| rabbitmq-default-user-credential-updater-iamguarded (plus FIPS) are net new images. |
|
|
|
|
7. | iamguarded-charts/valkey |
|
| valkey-iamguarded (plus FIPS) and valkey-sentinel-iamguarded (plus FIPS) are net new images. |
|
|
|
|
8. | iamguarded-charts/redis |
|
|
|
|
|
|
|
9. | iamguarded-charts/redis-cluster |
|
|
|
|
|
|
|
10. | iamguarded-charts/etcd |
|
|
|
|
|
|
|
11. | iamguarded-charts/contour |
|
| envoy-iamguarded is a net new image. |
|
|
|
|
12. | iamguarded-charts/mysql |
|
|
|
|
|
|
|
13. | iamguarded-charts/prometheus |
|
|
|
|
|
|
|
14. | iamguarded-charts/clickhouse |
|
| clickhouse-keeper-iamguarded is a net new image. |
|
|
|
|
15. | iamguarded-charts/minio |
|
|
|
|
|
|
|
16. | iamguarded-charts/kubernetes-event-exporter |
|
|
|
|
|
|
|
17. | iamguarded-charts/airflow |
|
| prometheus-statsd-exporter-iamguarded is a net new image. |
|
|
|
|
18. | iamguarded-charts/logstash |
|
|
|
|
|
|
|
19. | iamguarded-charts/zookeeper |
|
|
|
|
|
|
|
20. | iamguarded-charts/nginx |
|
| git-iamguarded is a net new image. |
|
|
|
|
21. | iamguarded-charts/cert-manager |
|
|
|
|
|
|
|
22. | iamguarded-charts/mlflow |
|
| git-iamguarded is a net new image. |
|
|
|
|
23. | iamguarded-charts/mongodb |
|
|
|
|
|
|
|
24. | iamguarded-charts/mongodb-sharded |
|
| mongodb-sharded-iamguarded is a net new image. |
|
|
|
|
25. | iamguarded-charts/external-dns |
|
|
|
|
|
|
|
26. | iamguarded-charts/flux |
|
| flux-image-automation-controller-iamguarded and flux-image-reflector-controller-iamguarded are net new images. |
|
|
|
|
27. | iamguarded-charts/influxdb |
|
| aws-cli-iamguarded, az-iamguarded, and google-cloud-sdk-iamguarded are net new images. |
|
|
|
|
28. | iamguarded-charts/keycloak |
|
|
|
|
|
|
|
29. | iamguarded-charts/kube-state-metrics |
|
|
|
|
|
|
|
30. | iamguarded-charts/metrics-server |
|
|
|
|
|
|
|
31. | iamguarded-charts/nginx-ingress-controller |
|
|
|
|
|
|
|
32. | iamguarded-charts/node-exporter |
|
|
|
|
|
|
|
33. | iamguarded-charts/spark |
|
|
|
|
|
|
|
34. | iamguarded-charts/thanos |
|
|
|
|
|
|
|
35. | iamguarded-charts/kafka |
|
|
|
|
|
|
|
36. | iamguarded-charts/superset |
|
| superset-iamguarded is a net new image. |
|
|
|
|
37. | iamguarded-charts/postgresql-ha |
|
|
|
|
|
|
|
38. | iamguarded-charts/grafana-mimir |
|
|
|
|
|
|
|
39. | iamguarded-charts/kube-prometheus |
|
| prometheus-blackbox-exporter-iamguarded and prometheus-operator-iamguarded are net new images. |
|
|
|
|
Q: Need help or have more questions?
A: We’re here for you. Just drop us a line at support.chainguard.dev and we’ll be happy to help.
Comments
0 comments
Article is closed for comments.