GitHub user dosubot[bot] added a comment to the discussion: How to connect to external redis db database? Using supersetNode.connections
<!-- Answer --> Your Redis authentication is failing because the Helm chart expects all Redis connection details—including the password—to be set in `values.yaml` under `supersetNode.connections`. Injecting `REDIS_PASSWORD` via `extraEnvFrom` alone does not update the config used by Superset; the chart-generated config only includes the password if you set `redis_password` in `values.yaml` [source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/helm/superset/templates/secret-env.yaml). Mixing config sources (values.yaml and extraEnvFrom) can cause missing or conflicting variables, leading to authentication errors [source](https://github.com/apache/superset/discussions/34861). For a reliable setup, use one of these patterns: 1. **Set the password in `values.yaml`** (preferred for Helm compatibility): ```yaml supersetNode: connections: redis_host: "your-redis-host" redis_port: "25061" redis_cache_db: "2" redis_celery_db: "2" redis_user: "" redis_password: "yourpassword" # reference your secret here if templating redis_ssl: enabled: true ssl_cert_reqs: "required" ``` This ensures the chart generates the correct environment variables and config for all pods. 2. **Full custom config:** If you must use a Kubernetes secret for the password, create a secret containing your own `superset_config.py` and set `configFromSecret` in `values.yaml` to the name of that secret. You must then include all required settings yourself [source](https://github.com/apache/superset/discussions/34861). Avoid mixing `extraEnvFrom` and `configOverrides` for Redis credentials. Stick to one method to prevent conflicts. After updating your config, redeploy all Superset pods. If your Redis requires a username, set `redis_user` in `values.yaml` and reference it in your config. If you still see authentication errors, double-check the actual Redis connection string used at runtime and ensure all pods have the correct environment variables [source](https://github.com/apache/superset/discussions/34650). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/1e331c18-ffe0-4866-8db6-0a57935d519c?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1e331c18-ffe0-4866-8db6-0a57935d519c?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1e331c18-ffe0-4866-8db6-0a57935d519c?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1e331c18-ffe0-4866-8db6-0a57935d519c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1e331c18-ffe0-4866-8db6-0a57935d519c?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1e331c18-ffe0-4866-8db6-0a57935d519c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1e331c18-ffe0-4866-8db6-0a57935d519c?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/35496) GitHub link: https://github.com/apache/superset/discussions/35496#discussioncomment-14587947 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
