You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "Kranthi32 (via GitHub)" <gi...@apache.org> on 2025/06/26 23:30:43 UTC
[D] For production configuration with Azure Kubernetes using heml but gett issues [superset]
GitHub user Kranthi32 created a discussion: For production configuration with Azure Kubernetes using heml but gett issues
### Bug description
Getting below error prodution setup just i used my external db postgre credentials and admin user details but hetting this continues can any support to set up production configuration in aks
PS C:\Users\102583\Documents\superset-aks-setup> helm upgrade superset apache/superset -f my-values.yaml -n default
Error: UPGRADE FAILED: post-upgrade hooks failed: 1 error occurred:
* timed out waiting for the condition
getting crash loop error
Please support
PS C:\Users\102583\Documents\superset-aks-setup> kubectl get pods
NAME READY STATUS RESTARTS AGE
superset-64b859fb4f-2cd2h 0/1 CrashLoopBackOff 9 (119s ago) 25m
superset-7498bb6bdd-j2spb 0/1 PodInitializing 0 6m22s
superset-init-db-92pmw 0/1 PodInitializing 0 6m22s
superset-postgresql-0 1/1 Running 0 25m
superset-redis-master-0 1/1 Running 0 25m
superset-worker-6cd68fb856-6zr49 0/1 PodInitializing 0 6m22s
superset-worker-8694794c6c-v6mp6 0/1 CrashLoopBackOff 9 (3m18s ago) 25m
PS C:\Users\102583\Documents\superset-aks-setup>
My-valies.yaml
my superset aks getting issues first with by default configuration we will try
please correct it this
postgresql:
postgresqlPassword: superset
configOverrides:
secret: |
SECRET_KEY = 'OG6tANx8xP8QAo9sabJAwUAjUs2OO7hEPmTqjgxqnj5TnjLouQP1tULQ'
configOverrides:
my_override: |
PREVIOUS_SECRET_KEY = 'YOUR_PREVIOUS_SECRET_KEY'
SECRET_KEY = 'YOUR_OWN_RANDOM_GENERATED_SECRET_KEY'
init:
command:
- /bin/sh
- -c
- |
. {{ .Values.configMountPath }}/superset_bootstrap.sh
superset re-encrypt-secrets
. {{ .Values.configMountPath }}/superset_init.sh
### 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.
GitHub link: https://github.com/apache/superset/discussions/33941
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] For production configuration with Azure Kubernetes using heml but gett issues [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
GitHub user rusackas added a comment to the discussion: For production configuration with Azure Kubernetes using heml but gett issues
A) The bot sounds pretty right here
B) This is more of a config issue than a bug, so I'll move it to a discussion
C:\ We don't officially support windows... but if you help add docs and support/fixes, maybe we can in the future!
GitHub link: https://github.com/apache/superset/discussions/33941#discussioncomment-13591558
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] For production configuration with Azure Kubernetes using heml but gett issues [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: For production configuration with Azure Kubernetes using heml but gett issues
<!-- Answer -->
Your my-values.yaml has a few issues that are likely causing the CrashLoopBackOff and upgrade failures:
- Only use one configOverrides section. Multiple configOverrides keys will break the YAML and cause Helm to deploy with incomplete config, leading to pod failures. Combine your overrides into a single configOverrides block as shown in the Helm chart docs ["configOverrides"](https://github.com/apache/superset/blob/a56d7252c2470ff0e6f51e72610c752ee1968d18/helm/superset/values.yaml).
- The PostgreSQL password should be set under postgresql.auth.password, not postgresql.postgresqlPassword. The correct structure is:
```yaml
postgresql:
auth:
password: superset
```
See the Helm chart's [values.yaml](https://github.com/apache/superset/blob/a56d7252c2470ff0e6f51e72610c752ee1968d18/helm/superset/values.yaml) for reference.
- Set a secure, unique SECRET_KEY for production. You can do this via either extraSecretEnv.SUPERSET_SECRET_KEY or configOverrides.secrets, but not both. Example:
```yaml
configOverrides:
secrets: |
SECRET_KEY = 'your-strong-random-secret'
```
Or:
```yaml
extraSecretEnv:
SUPERSET_SECRET_KEY: 'your-strong-random-secret'
```
See ["SECRET_KEY"](https://github.com/apache/superset/blob/a56d7252c2470ff0e6f51e72610c752ee1968d18/helm/superset/README.md).
- If you are using an external PostgreSQL database, you must ensure the required Python and system dependencies are installed. Add a bootstrapScript to your values file:
```yaml
bootstrapScript: |
#!/bin/bash
apt update && apt install -y gcc libpq-dev python3-dev pkg-config
pip install psycopg2-binary
```
See [discussion on missing dependencies](https://github.com/apache/superset/discussions/31432).
- Increase the Helm timeout with --timeout 10m0s to avoid premature failures during initialization ["timeout"](https://github.com/apache/superset/discussions/31500).
- Check logs from the crashing pods with kubectl logs <pod-name> to identify any remaining issues, such as missing dependencies or DB connection errors.
After making these changes, try redeploying. If you still see issues, check network connectivity from AKS to your external PostgreSQL and ensure all required secrets and environment variables are present.
<!-- 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/7b872367-edf0-43e2-b449-67092b8c262d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7b872367-edf0-43e2-b449-67092b8c262d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7b872367-edf0-43e2-b449-67092b8c262d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7b872367-edf0-43e2-b449-67092b8c262d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7b872367-edf0-43e2-b449-67092b8c262d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7b872367-edf0-43e2-b449-67092b8c262d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7b872367-edf0-43e2-b449-67092b8c262d?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/33938)
GitHub link: https://github.com/apache/superset/discussions/33941#discussioncomment-13591557
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] For production configuration with Azure Kubernetes using heml but gett issues [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: For production configuration with Azure Kubernetes using heml but gett issues
<!-- Answer -->
Your my-values.yaml has a few issues that are likely causing the CrashLoopBackOff and upgrade failures:
- Only use one configOverrides section. Multiple configOverrides keys will break the YAML and cause Helm to deploy with incomplete config, leading to pod failures. Combine your overrides into a single configOverrides block as shown in the Helm chart docs ["configOverrides"](https://github.com/apache/superset/blob/a56d7252c2470ff0e6f51e72610c752ee1968d18/helm/superset/values.yaml).
- The PostgreSQL password should be set under postgresql.auth.password, not postgresql.postgresqlPassword. The correct structure is:
```yaml
postgresql:
auth:
password: superset
```
See the Helm chart's [values.yaml](https://github.com/apache/superset/blob/a56d7252c2470ff0e6f51e72610c752ee1968d18/helm/superset/values.yaml) for reference.
- Set a secure, unique SECRET_KEY for production. You can do this via either extraSecretEnv.SUPERSET_SECRET_KEY or configOverrides.secrets, but not both. Example:
```yaml
configOverrides:
secrets: |
SECRET_KEY = 'your-strong-random-secret'
```
Or:
```yaml
extraSecretEnv:
SUPERSET_SECRET_KEY: 'your-strong-random-secret'
```
See ["SECRET_KEY"](https://github.com/apache/superset/blob/a56d7252c2470ff0e6f51e72610c752ee1968d18/helm/superset/README.md).
- If you are using an external PostgreSQL database, you must ensure the required Python and system dependencies are installed. Add a bootstrapScript to your values file:
```yaml
bootstrapScript: |
#!/bin/bash
apt update && apt install -y gcc libpq-dev python3-dev pkg-config
pip install psycopg2-binary
```
See [discussion on missing dependencies](https://github.com/apache/superset/discussions/31432).
- Increase the Helm timeout with --timeout 10m0s to avoid premature failures during initialization ["timeout"](https://github.com/apache/superset/discussions/31500).
- Check logs from the crashing pods with kubectl logs <pod-name> to identify any remaining issues, such as missing dependencies or DB connection errors.
After making these changes, try redeploying. If you still see issues, check network connectivity from AKS to your external PostgreSQL and ensure all required secrets and environment variables are present.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=97297df7-bbec-4f48-9368-f7c409cbeba4) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/33941#discussioncomment-13591557
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org