bring up kube-system cluster

[#1]

Waiting for 10 seconds before checking again...
Some pods in kube-system have not yet started. This may take a few minutes.
Waiting for 10 seconds before checking again...

ERROR:: Unable to bring up kube-system cluster.: 1

ERROR:: Unable to start clusters: 1
[root@master~]# cdsw status
Cloudera Data Science Workbench Status

Service Status
docker: active
kubelet: active
nfs: active
Checking kernel parameters...

Node Status
NAME STATUS AGE STATEFUL
cdh-mn-511-ce1.eoh.com Ready 31m <none>

System Pod status
NAME READY STATUS RESTARTS AGE IP NODE
dummy-2088944543-13mzy 1/1 Running 0 31m 10.10.51.250 cdh-mn-511-ce1.eoh.com
etcd-cdh-mn-511-ce1.eoh.com 1/1 Running 0 31m 10.10.51.250 cdh-mn-511-ce1.eoh.com
kube-apiserver-cdh-mn-511-ce1.eoh.com 1/1 Running 2 30m 10.10.51.250 cdh-mn-511-ce1.eoh.com
kube-controller-manager-cdh-mn-511-ce1.eoh.com 1/1 Running 0 30m 10.10.51.250 cdh-mn-511-ce1.eoh.com
kube-discovery-1150918428-aqryf 1/1 Running 0 31m 10.10.51.250 cdh-mn-511-ce1.eoh.com
kube-dns-654381707-aw62w 2/3 CrashLoopBackOff 11 31m 100.66.0.2 cdh-mn-511-ce1.eoh.com
kube-proxy-mksfc 1/1 Running 0 31m 10.10.51.250 cdh-mn-511-ce1.eoh.com
kube-scheduler-cdh-mn-511-ce1.eoh.com 1/1 Running 0 30m 10.10.51.250 cdh-mn-511-ce1.eoh.com
weave-net-qjxuf 2/2 Running 0 31m 10.10.51.250 cdh-mn-511-ce1.eoh.com

Cloudera Data Science Workbench Pod Status

WARNING: Unable to get details for role [cron].
Cloudera Data Science Workbench is not ready yet: the cluster specification is incomplete

[#2]

[root@master ~]# cdsw logs
Generating Cloudera Data Science Workbench diagnostic bundle...
Checking system basics...
Saving kernel parameters...
Checking validation output...
Checking application configuration...
Checking disks...
Checking Hadoop configuration...
Checking network...
Checking system services...
Checking Docker...
Checking Kubernetes...
Checking Kubelet...
Checking application services...
Checking cluster info...
Checking app cluster info...
Exporting user ids...
Error from server: configmaps "internal-config" not found
error: pod name must be specified
Checking system logs...
Producing logs tarball...
Logs saved to: 

[#3]

Hi NES,

We saw similar issues that the kube-dns pod is not coming online properly when you configure proxy without excluding the local traffic.

You can find an example NO_PROXY configuration in the documentation:

https://www.cloudera.com/documentation/data-science-workbench/latest/topics/cdsw_install.html#instal...

Regards,

Peter

[#4]

thanks, installation completed after adding NO_PROXY

now my cdsw status command is showing that some pods are no ready.

Cloudera Data Science Workbench is not ready yet: some system pods are not ready
[root@mater ~]#