Descripción del problema:
Kube-apiserver auto-prueba no pasa la inspección se encontró ningún puerto de escucha 8443
[root@openshift openshift]# oc cluster up
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
error: did not detect an --insecure-registry argument on the Docker daemon
[root@openshift openshift]# oc cluster up --skip-registry-check=true
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I0629 03:24:23.893461 51057 flags.go:30] Running "create-kubelet-flags"
I0629 03:24:24.226490 51057 run_kubelet.go:49] Running "start-kubelet"
I0629 03:24:24.390056 51057 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0629 03:29:24.392998 51057 run_self_hosted.go:571] API server error: Get https://127.0.0.1:8443/healthz?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused ()
Error: timed out waiting for the condition
[root@openshift openshift]#
Socket error Event: 32 Error: 10053.
Connection closing...Socket close.
Connection closed by foreign host.
Disconnected from remote host(centOS) at 18:38:11.
[root@openshift openshift]# oc cluster up --skip-registry-check=true
Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Checking type of volume mount ...
Determining server IP ...
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11 ...
I0629 03:47:17.628873 39759 config.go:40] Running "create-master-config"
I0629 03:47:24.909524 39759 config.go:46] Running "create-node-config"
I0629 03:47:28.147522 39759 flags.go:30] Running "create-kubelet-flags"
I0629 03:47:28.693783 39759 run_kubelet.go:49] Running "start-kubelet"
I0629 03:47:28.844126 39759 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0629 03:52:45.569132 39759 run_self_hosted.go:571] API server error: an error on the server ("[+]ping ok\n[+]log ok\n[+]etcd ok\n[+]poststarthook/generic-apiserver-start-informers ok\n[+]poststarthook/start-apiextensions-informers ok\n[+]poststarthook/start-apiextensions-controllers ok\n[-]poststarthook/bootstrap-controller failed: reason withheld\n[-]poststarthook/rbac/bootstrap-roles failed: reason withheld\n[-]poststarthook/scheduling/bootstrap-system-priority-classes failed: reason withheld\n[-]poststarthook/ca-registration failed: reason withheld\n[+]poststarthook/start-kube-apiserver-informers ok\n[+]poststarthook/start-kube-apiserver-admission-initializer ok\n[+]poststarthook/quota.openshift.io-clusterquotamapping ok\n[+]poststarthook/oauth.openshift.io-startoauthclientsbootstrapping ok\n[+]poststarthook/openshift.io-startkubeinformers ok\n[+]poststarthook/start-kube-aggregator-informers ok\n[+]poststarthook/apiservice-registration-controller ok\n[+]poststarthook/apiservice-status-available-controller ok\n[+]poststarthook/apiservice-openapi-controller ok\n[+]poststarthook/kube-apiserver-autoregistration ok\n[-]autoregister-completion failed: reason withheld\nhealthz check failed") has prevented the request from succeeding ()
Error: timed out waiting for the condition
soluciones
Desactivar el firewall Referencia https://blog.csdn.net/ytangdigl/article/details/79796961
Después de comprobar el buque comenzó la instalación
Puntero para empezar a comprobar el contenedor, de la siguiente manera:
