Repository navigation
Bitnami images used in Helm chart are not available #4172
Copy link
Copy link
Open
Description
Preflight Checklist
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
- I am not looking for support or already pursued the available support channels without success.
OpenMeter Version
1.0.0-beta.227
Expected Behavior
Running
kind create cluster
kubectl cluster-info --context kind-kind
helm upgrade --install openmeter oci://ghcr.io/openmeterio/helm-charts/openmeter --version 1.0.0-beta.227
should start full openmeter stack properly
Actual Behavior
Bitnami images are not pulled :
guillaume@nixos ~> helm upgrade --install openmeter oci://ghcr.io/openmeterio/helm-charts/openmeter --version 1.0.0-beta.227
Release "openmeter" does not exist. Installing it now.
Pulled: ghcr.io/openmeterio/helm-charts/openmeter:1.0.0-beta.227
Digest: sha256:d21a051ab1025a905ca372d561a4e5bbbb27d1861c42627edfeffaf7f02ee87e
coalesce.go:237: warning: skipped value for kafka.config: Not a table.
I0419 00:12:59.932549 45148 warnings.go:107] "Warning: spec.template.spec.containers[1].ports[0]: duplicate port name \"metrics\" with spec.template.spec.containers[0].ports[0], services and probes that select ports by name will use spec.template.spec.containers[0].ports[0]"
NAME: openmeter
LAST DEPLOYED: Sun Apr 19 00:12:58 2026
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Thank you for installing OpenMeter!
It is highly recommended to use your own Postgres for production deployments!
It is highly recommended to use your own Clickhouse for production deployments!
It is highly recommended to use your own ClickHouse for production deployments!
It is highly recommended to use your own Kafka for production deployments!
It is highly recommended to use your own Redis for production deployments!
It is highly recommended to use your own Svix for production deployments!
guillaume@nixos ~> kubectl get pods
NAME READY STATUS RESTARTS AGE
openmeter-altinity-clickhouse-operator-d96c87cb9-h2f6b 2/2 Running 0 26s
openmeter-api-764d7c9685-7j2s7 0/1 Init:0/2 0 26s
openmeter-balance-worker-55b4cc6f9d-tn47z 0/1 Init:0/2 0 26s
openmeter-billing-worker-6dd9c44854-qvlqr 0/1 Init:0/2 0 26s
openmeter-kafka-controller-0 0/1 Init:ErrImagePull 0 25s
openmeter-kafka-controller-1 0/1 Init:ErrImagePull 0 25s
openmeter-kafka-controller-2 0/1 Init:ErrImagePull 0 25s
openmeter-notification-service-696fdcdf86-ppkv7 0/1 Init:0/2 0 26s
openmeter-postgres-0 0/1 ErrImagePull 0 25s
openmeter-redis-master-0 0/1 ErrImagePull 0 25s
openmeter-redis-replicas-0 0/1 ErrImagePull 0 25s
openmeter-sink-worker-59bf66656-6r9l5 0/1 Init:0/2 0 26s
openmeter-svix-559bdcdcc8-sngk5 0/1 Init:0/2 0 26s
In fact they don't exist at all, I guess due to Bitnami stopping to release public versioned debian images ?
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 3m59s default-scheduler Successfully assigned default/openmeter-kafka-controller-0 to kind-control-plane
Normal Pulling 68s (x5 over 3m58s) kubelet spec.initContainers{kafka-init}: Pulling image "docker.io/bitnami/kafka:3.8.1-debian-12-r0"
Warning Failed 68s (x5 over 3m54s) kubelet spec.initContainers{kafka-init}: Failed to pull image "docker.io/bitnami/kafka:3.8.1-debian-12-r0": rpc error: code = NotFound desc = failed to pull and unpack image
"docker.io/bitnami/kafka:3.8.1-debian-12-r0": failed to resolve reference "docker.io/bitnami/kafka:3.8.1-debian-12-r0": docker.io/bitnami/kafka:3.8.1-debian-12-r0: not found
Warning Failed 68s (x5 over 3m54s) kubelet spec.initContainers{kafka-init}: Error: ErrImagePull
Normal BackOff 11s (x13 over 3m54s) kubelet spec.initContainers{kafka-init}: Back-off pulling image "docker.io/bitnami/kafka:3.8.1-debian-12-r0"
Warning Failed 11s (x13 over 3m54s) kubelet spec.initContainers{kafka-init}: Error: ImagePullBackOff
Steps To Reproduce
kind create cluster
kubectl cluster-info --context kind-kind
helm upgrade --install openmeter oci://ghcr.io/openmeterio/helm-charts/openmeter --version 1.0.0-beta.227
kubectl get pods
Additional Information
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
ankitk0305 commentedon Apr 19, 2026
I am working on this
fix(helm): redirect Bitnami images to registry.bitnami.com
fix(helm): bump Bitnami sub-chart versions to fix image pull failures