Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Because of changes made with bitnami

the epinio services that are using the bitnami charts in the service catalog don't work. So basically none of the out of the box ones are working at the moment.

Expected Behavior

it should deploy the helm charts successfully

Steps To Reproduce

• setup kind cluster with cert-manager and ingress-nginx. here is how I currently do this link to gist

• then install epinio onto kind cluster

cat <<'EOF' | helm upgrade --install epinio epinio/epinio \
  --namespace epinio \
  --create-namespace \
  --values -
global:
  domain: localhost
ingress:
  annotations:
    cert-manager.io/cluster-issuer: quick-kind-ca
EOF

Environment

- OS: Linux
- Architecture: x86_64
- Epinio Version: 1.13.0
- Cluster:
  - Provider: KinD
  - Options: 1 master, 1 worker, rancher.io/local-path, no lb just ingress-nginx -> node port
  - Kubernetes Version: 1.34.0

Logs

Anything else?

To Fix Issue

I would first try and update the images used by the charts to a non bitnami image. honestly the official ones on dockerhub or from suse registry (they dont have rabbitmq, mysql,

run something along the line of these commands to find where the images are in the values file for each chart

helm show values bitnami/postgresql --version 12.1.6 | grep -m1 -A 10 -B 10 -E '^[[:space:]]*image:'
helm show values bitnami/mysql --version 9.4.5 | grep -m1 -A 10 -B 10 -E '^[[:space:]]*image:'
helm show values bitnami/redis --version 17.3.17 | grep -m1 -A 10 -B 10 -E '^[[:space:]]*image:'
helm show values bitnami/rabbitmq --version 11.2.2 | grep -m1 -A 10 -B 10 -E '^[[:space:]]*image:'
helm show values bitnami/mongodb --version 13.6.2 | grep -m1 -A 10 -B 10 -E '^[[:space:]]*image:'

here are links to the dockerhub repos for convenience

postgres
rabbitmq
mysql
redis
mongo

and if after updating the images, it works, then sweet! problem fixed 😎.

BUT...., if some unexpected issue(s) come up with bitnami chart and non-bitnami images, then I would look at changing chart used. But I wouldn't do all that initially, unless it's actually needed.