The CDSW showed good health after following these steps. But I think we have an issue with the DNS. After sometimes it is again going to bad health. This is the logs: Pods not ready in cluster kube-system ['k8s-app/kube-dns', 'k8s-app/kube-proxy', 'component/kube-scheduler', 'name/weave-net', 'name/tiller']. Pods not ready in cluster default ['role/cron', 'role/db', 'role/ds-operator', 'role/ds-reconciler', 'role/ds-vfs', 'role/ingress-controller', 'role/livelog', 'role/s2i-builder', 'role/s2i-client', 'role/s2i-git-server', 'role/s2i-queue', 'role/s2i-registry-auth', 'role/s2i-registry', 'role/s2i-server', 'role/secret-generator', 'role/tcp-ingress-controller', 'role/web', 'role/spark-port-forwarder', 'role/ds-cdh-client']. Application services are incomplete. [web, db, livelog] not found. Secrets are incomplete. [internal-secrets, external-secrets] not found. Persistent volumes are incomplete. Persistent volume claims are incomplete. Ingresses are incomplete. Checking web at url: http://cdsw.company.io Web is not yet up. Cloudera Data Science Workbench is not ready yet For setting up DNS wildcards, I have configured the domain to CDSW's public IP (Elastic IP in AWS). Is that correct? Because we can't use private IPs in the subdomain, right? What is this line in the Cloudera document means: The wildcard DNS hostname configured for Cloudera Data Science Workbench must now be resolvable from both, the CDSW cluster, and your browser.
... View more
