openshift
Minishift 1.34.3 error on windows 10
I constantly get this error of connection timeout:
Starting OpenShift using openshift/origin-control-plane:v3.11.0 ... I0726 17:05:57.026621 2804 config.go:40] Running "create-master-config" I0726 17:06:09.817949 2804 config.go:46] Running "create-node-config" I0726 17:06:13.475457 2804 flags.go:30] Running "create-kubelet-flags" I0726 17:06:14.563162 2804 run_kubelet.go:49] Running "start-kubelet" I0726 17:06:15.051573 2804 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ... E0726 17:11:28.066790 2804 run_self_hosted.go:571] API server error: Get https://192.168.99.103:8443/healthz?timeout=32s: net/http: TLS handshake timeout () Error: timed out waiting for the condition
minishift status shows this: E:\coding\minishift-1.34.3-windows-amd64>minishift status Minishift: Running Profile: minishift OpenShift: Running (openshift v3.11.0+07ae5a0-606) DiskUsage: 11% of 19G (Mounted On: /mnt/sda1) CacheUsage: 512.9 MB (used by oc binary, ISO or cached images)
when checked in ssh only the kube-api-server container is exited. i verified the resources and there is not starvation.
i would be glad if anyone can help me on this issue.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale