[ https://issues.jboss.org/browse/JBIDE-26562?page=com.atlassian.jira.plugi... ] Andreas Gajdosik commented on JBIDE-26562: ------------------------------------------ [~adietish] If you mean something like this: {code} I0207 09:15:48.086798 8399 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ... E0207 09:20:48.093349 8399 run_self_hosted.go:571] API server error: Get https://192.168.99.100:8443/healthz?timeout=32s: dial tcp 192.168.99.100:8443: connect: connection refused () Error: timed out waiting for the condition {code} then yes, this is a known issue. You can comment here: https://issues.jboss.org/browse/CDK-389 that it also affects you on Mac. However it originates from OpenShift -Origin- OKD https://github.com/openshift/origin/issues/20617 (you can also comment there to draw some attention, but I lost hope). This issue with cluster-up was reported by me on 13 Aug 2018, it has 25 participants, however it was ignored by OKD team for months and then closed with non-working fix. As karma bumerang it comes back and affects cluster-up and whole CDK, renders it unusable for some devs. -- This message was sent by Atlassian Jira (v7.12.1#712002)