Default values.yaml for helm chart does not work (image pull errors)

[dmitrynovik]

Bug description

1. Download values.yaml from https://github.com/apache/superset/blob/master/helm/superset/values.yaml
2. Run helm upgrade --install --values values.yaml superset superset/superset as described

Expected: default installation works Actual: image pull errors for redis and postgres

superset-6cfd5b6684-k9699          0/1     Init:0/1           16 (5m9s ago)    18h
superset-init-db-c7bch             0/1     Init:Error         0                3m28s
superset-init-db-czrtf             0/1     Init:0/1           0                96s
superset-init-db-pt2f6             0/1     Init:Error         0                5m20s
superset-postgresql-0              0/1     ImagePullBackOff   0                30m
superset-redis-master-0            0/1     ImagePullBackOff   0                30m
superset-worker-78c4d4fbd6-zbdg8   0/1     Init:0/1           16 (5m19s ago)   18h

kubectl describe pod superset-redis-master-0 | grep -i image
    Image:         docker.io/bitnami/redis:7.0.10-debian-11-r4
    Image ID:
      Reason:       ImagePullBackOff
  Normal   Pulling    31m (x4 over 32m)    kubelet            Pulling image "docker.io/bitnami/redis:7.0.10-debian-11-r4"
  Warning  Failed     31m (x4 over 32m)    kubelet            Failed to pull image "docker.io/bitnami/redis:7.0.10-debian-11-r4": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/bitnami/redis:7.0.10-debian-11-r4": failed to resolve reference "docker.io/bitnami/redis:7.0.10-debian-11-r4": docker.io/bitnami/redis:7.0.10-debian-11-r4: not found
  Warning  Failed     31m (x4 over 32m)    kubelet            Error: ErrImagePull
  Warning  Failed     30m (x6 over 32m)    kubelet            Error: ImagePullBackOff
  Normal   BackOff    19s (x152 over 32m)  kubelet            Back-off pulling image "docker.io/bitnami/

 kubectl describe pod superset-postgresql-0 | grep -i image
    Image:           docker.io/bitnami/postgresql:14.17.0-debian-12-r3
    Image ID:
      Reason:        ImagePullBackOff
  Normal   Pulling    32m (x4 over 34m)     kubelet            Pulling image "docker.io/bitnami/postgresql:14.17.0-debian-12-r3"
  Warning  Failed     32m (x4 over 34m)     kubelet            Failed to pull image "docker.io/bitnami/postgresql:14.17.0-debian-12-r3": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/bitnami/postgresql:14.17.0-debian-12-r3": failed to resolve reference "docker.io/bitnami/postgresql:14.17.0-debian-12-r3": docker.io/bitnami/postgresql:14.17.0-debian-12-r3: not found
  Warning  Failed     32m (x4 over 34m)     kubelet            Error: ErrImagePull
  Warning  Failed     32m (x6 over 34m)     kubelet            Error: ImagePullBackOff
  Normal   BackOff    106s (x151 over 34m)  kubelet            Back-off pulling image "docker.io/bitnami/postgresql:14.17.0-debian-12-r3"

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
• [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
• [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot[bot]]

Hi @dmitrynovik! I'm Dosu and I’m helping the superset team.

The image pull errors are happening because Bitnami has moved many Redis and PostgreSQL images behind a paywall or to a legacy repository, so the default image tags in the Helm chart (bitnami/redis:7.0.10-debian-11-r4 and bitnami/postgresql:14.17.0-debian-12-r3) are no longer available on Docker Hub. This is a known issue and is being tracked in several open issues and discussions (#34414, #35461, #35688).

Temporary workaround:
Override the image repository in your values.yaml to use the Bitnami legacy repo. For example:

postgresql:
  image:
    repository: bitnamilegacy/postgresql
    tag: "14.17.0-debian-12-r3"

redis:
  image:
    repository: bitnamilegacy/redis
    tag: "7.0.10-debian-11-r4"

After updating, make sure to delete the pods stuck in ImagePullBackOff so new ones are created with the updated images.

Long-term solution:
Switch to official Docker images or build your own custom images for Redis and PostgreSQL. The Superset Helm chart is moving away from Bitnami dependencies (PR #36174), but until a new release is published, manual overrides are needed.

Note:
If you hit Python dependency errors (like missing redis or psycopg2-binary), the robust solution is to build a custom Superset Docker image with all required dependencies pre-installed and update your values.yaml to use it. This avoids runtime install issues and is best practice for production (discussion).

This is a community-maintained chart, so fixes and updates depend on community contributions. For ongoing updates, follow the linked issues above.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[chgl]

You'll also need to set

global:
  security:
    allowInsecureImages: true

[rusackas]

^ Does that solve it? Maybe we just need some documentation updates?

CC @villebro

[dmitrynovik]

^ Does that solve it? Maybe we just need some documentation updates?

CC @villebro

No. Or yes but it is only getting me to the next issue: ModuleNotFoundError: No module named 'psycopg2' which is already submitted: https://github.com/apache/superset/issues/35174

Looks like the Helm chart for superset is seriously broken.