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/07/16 08:54:37 UTC

[D] Unable to run superset with nginx ingress getting dial tcp 10.9.0.135:0->20.235.237.100:80: i/o timeout [superset]

GitHub user Kranthi32 created a discussion: Unable to run superset with nginx ingress getting dial tcp 10.9.0.135:0->20.235.237.100:80: i/o timeout

with nginx ingrees i am getting dial tcp 10.9.0.135:0->20.235.201.100:80: i/o timeout


my values.yaml is

configOverrides:
  superset_config.py: |
    import os
    from urllib.parse import quote_plus
    from flask_caching import Cache

    ENABLE_PROXY_FIX = True
    SUPERSET_WEBSERVER_BASEURL = "http://superset.20.235.201.100.nip.io"

    DB_USER = os.getenv("DB_USER")
    DB_PASS = os.getenv("DB_PASS")
    DB_HOST = os.getenv("DB_HOST")
    DB_PORT = os.getenv("DB_PORT")
    DB_NAME = os.getenv("DB_NAME")

    SQLALCHEMY_DATABASE_URI = (
        f"postgresql+psycopg2://{quote_plus(DB_USER)}:{quote_plus(DB_PASS)}@{DB_HOST}:{DB_PORT}/{DB_NAME}?sslmode=require"
    )

    RESULTS_BACKEND = Cache(
        config={
            'CACHE_TYPE': 'RedisCache',
            'CACHE_DEFAULT_TIMEOUT': 300,
            'CACHE_KEY_PREFIX': 'superset_results',
            'CACHE_REDIS_URL': 'redis://superset-redis-master:6379/0'
        }
    )

    FILTER_STATE_CACHE_CONFIG = {
        "CACHE_TYPE": "RedisCache",
        "CACHE_DEFAULT_TIMEOUT": 300,
        "CACHE_KEY_PREFIX": "superset_filter_state",
        "CACHE_REDIS_URL": "redis://superset-redis-master:6379/0"
    }

    EXPLORE_FORM_DATA_CACHE_CONFIG = {
        "CACHE_TYPE": "RedisCache",
        "CACHE_DEFAULT_TIMEOUT": 300,
        "CACHE_KEY_PREFIX": "superset_explore_form",
        "CACHE_REDIS_URL": "redis://superset-redis-master:6379/0"
    }

    TALISMAN_ENABLED = False
    TALISMAN_CONFIG = {
        "content_security_policy": {
            "default-src": ["'self'"],
            "img-src": ["'self'", "data:", "blob:"],
        }
    }

    ENABLE_PROXY_FIX = True
    SUPERSET_WEBSERVER_TIMEOUT = 300
    SUPERSET_WEBSERVER_ADDRESS = "0.0.0.0"

service:
  type: ClusterIP
  port: 8088
  targetPort: http 
  annotations: {}

ingress:
  enabled: true
  ingressClassName: nginx
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/ssl-redirect: "false"
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "300"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "300"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "300"
  path: /
  pathType: Prefix
  hosts:
    - superset.20.235.201.100.nip.io  
  tls: []
  
  
  my kubectl external ip is
  
  kubectl get ingress -n superset
NAME       CLASS   HOSTS                            ADDRESS          PORTS   AGE
superset   nginx   superset.20.235.237.100.nip.io   20.235.201.100   80      77s

>kubectl describe ingress -n superset
Name:             superset
Labels:           app=superset
                  app.kubernetes.io/managed-by=Helm
                  chart=superset-0.14.2
                  heritage=Helm
                  release=superset
Namespace:        superset
Address:          20.235.237.100
Ingress Class:    nginx
Default backend:  <default>
Rules:
  Host                            Path  Backends
  ----                            ----  --------
  superset.20.235.237.100.nip.io
                                  /   superset:http (10.244.2.224:8088)
Annotations:                      meta.helm.sh/release-name: superset
                                  meta.helm.sh/release-namespace: superset
                                  nginx.ingress.kubernetes.io/proxy-connect-timeout: 300
                                  nginx.ingress.kubernetes.io/proxy-read-timeout: 300
                                  nginx.ingress.kubernetes.io/proxy-send-timeout: 300
                                  nginx.ingress.kubernetes.io/rewrite-target: /
                                  nginx.ingress.kubernetes.io/ssl-redirect: false
Events:
  Type    Reason  Age                  From                      Message
  ----    ------  ----                 ----                      -------
  Normal  Sync    98s (x2 over 2m38s)  nginx-ingress-controller  Scheduled for sync

why i am getting this error please support @dosu 
  
  

GitHub link: https://github.com/apache/superset/discussions/34187

----
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] Unable to run superset with nginx ingress getting dial tcp 10.9.0.135:0->20.235.237.100:80: i/o timeout [superset]

Posted by "Kranthi32 (via GitHub)" <gi...@apache.org>.
GitHub user Kranthi32 added a comment to the discussion: Unable to run superset with nginx ingress getting dial tcp 10.9.0.135:0->20.235.237.100:80: i/o timeout

@dosu please support

GitHub link: https://github.com/apache/superset/discussions/34187#discussioncomment-13775308

----
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