groverkaushal commented on issue #25004: URL: https://github.com/apache/superset/issues/25004#issuecomment-2761120257
@accorvin Hi, I was having the same issue using minikube + helm chart. Turns out it was not CA certificate or SSL error issue. It was a DNS issue. when superset container was running as a Kubernetes Pod inside Minikube, its `/etc/resolv.conf` was overwritten by Kubernetes DNS settings. so to resolve this... once the pod is running you can ``` kubectl exec -it superset-xxxxxxxxx-xxxxx -- bash echo "nameserver 8.8.8.8" > /etc/resolv.conf ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
