GitHub user dosubot[bot] added a comment to the discussion: Production deployment issue in
<!-- Answer --> Your Helm config is close, but there are a few common issues that can cause CrashLoopBackOff and init-db errors with external PostgreSQL on Azure: 1. Make sure the Kubernetes secret superset-db-secret exists in your namespace and contains the db-password key with the correct value. If the secret or key is missing or misnamed, Superset can't connect to the DB and pods will fail to start ([source](https://github.com/apache/superset/issues/33938)). 2. Only use one configOverrides section in your values.yaml. Multiple configOverrides blocks will break the YAML and cause incomplete config, leading to pod failures ([source](https://github.com/apache/superset/discussions/33941)). 3. For external PostgreSQL, you must install system dependencies (gcc, libpq-dev, python3-dev, pkg-config) and psycopg2-binary in your bootstrapScript. Just pip install psycopg2-binary is often not enough—add the apt install line as well ([source](https://github.com/apache/superset/discussions/31432)): ```yaml bootstrapScript: | #!/bin/bash apt update && apt install -y gcc libpq-dev python3-dev pkg-config pip install psycopg2-binary ``` 4. Azure PostgreSQL usually requires SSL. If so, you need to add ?sslmode=require to your connection string. The Helm chart builds SQLALCHEMY_DATABASE_URI from env vars, so set DB_EXTRA_ARGS or use the externalDatabase.extraArgs field if available, or override with configOverrides if needed ([source](https://github.com/apache/superset/blob/ede3de0ca0addde195199be332d6e4dd454955ef/helm/superset/templates/_helpers.tpl)). 5. Check pod logs with kubectl logs <pod-name> for the actual error—this will tell you if it's a DB connection, missing dependency, or something else ([source](https://github.com/apache/superset/discussions/31500)). 6. If you see timeouts, try increasing your Helm install/upgrade timeout: --timeout 10m0s ([source](https://github.com/apache/superset/discussions/31500)). If you still have issues, please share the output of kubectl logs for the failing pods—this will help pinpoint the root cause. <!-- 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/e8034b79-2960-49f3-a3b4-5c8ec3468047?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e8034b79-2960-49f3-a3b4-5c8ec3468047?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e8034b79-2960-49f3-a3b4-5c8ec3468047?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e8034b79-2960-49f3-a3b4-5c8ec3468047?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e8034b79-2960-49f3-a3b4-5c8ec3468047?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e8034b79-2960-49f3-a3b4-5c8ec3468047?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e8034b79-2960-49f3-a3b4-5c8ec3468047?feedback_type=other)</sup> [](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/issues/33945) GitHub link: https://github.com/apache/superset/discussions/33957#discussioncomment-13599733 ---- 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]
