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.