Hello there,
I’m trying to install RKE and Rancher on top of it on a CentOS 7.8 machine. Followed steps as per documentation, disabled firewall with sample cluster.yml. RKE installation failed multiple times with different error each time, however running up command again and again helped.
Try 1: Failed
INFO[0291] [controlplane] Building up Controller Plane…
INFO[0291] Checking if container [service-sidekick] is running on host [192.168.168.224], try #1
INFO[0291] Image [rancher/rke-tools:v0.1.66] exists on host [192.168.168.224]
INFO[0295] Image [rancher/hyperkube:v1.19.4-rancher1] exists on host [192.168.168.224]
INFO[0300] Starting container [kube-apiserver] on host [192.168.168.224], try #1
INFO[0309] [controlplane] Successfully started [kube-apiserver] container on host [192.168.168.224]
INFO[0309] [healthcheck] Start Healthcheck on service [kube-apiserver] on host [192.168.168.224]
FATA[0360] [controlPlane] Failed to bring up Control Plane: [Failed to verify healthcheck: Service [kube-apiserver] is not healthy on host [192.168.168.224]. Response code: [403], response body: {“kind”:“Status”,“apiVersion”:“v1”,“metadata”:{},“status”:“Failure”,“message”:“forbidden: User “kube-apiserver” cannot get path “/healthz””,“reason”:“Forbidden”,“details”:{},“code”:403}
, log: Trace[780323755]: [599.829712ms] [599.829712ms] END]
Try 2: Failed
INFO[0618] [sync] Successfully synced nodes Labels and Taints
INFO[0618] [network] Setting up network plugin: canal
INFO[0618] [addons] Saving ConfigMap for addon rke-network-plugin to Kubernetes
INFO[0621] [addons] Successfully saved ConfigMap for addon rke-network-plugin to Kubernetes
INFO[0621] [addons] Executing deploy job rke-network-plugin
FATA[0675] Failed to get job complete status for job rke-network-plugin-deploy-job in namespace kube-system
Try 3: Failed - But noticed success message at the end
INFO[0478] [addons] Successfully saved ConfigMap for addon rke-ingress-controller to Kubernetes
INFO[0478] [addons] Executing deploy job rke-ingress-controller
WARN[0541] Failed to deploy addon execute job [rke-ingress-controller]: Failed to get job complete status for job rke-ingress-controller-deploy-job in namespace kube-system
INFO[0541] [addons] Setting up user addons
INFO[0541] [addons] no user addons defined
INFO[0541] Finished building Kubernetes cluster successfully
Try 4: No errors shown, however, when listing containers can notice two containers exited with code 0 as shown below.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
81e3ee37a584 4cbe1ed86c35 “/usr/local/bin/flex…” 7 minutes ago Exited (0) 7 minutes ago k8s_flexvol-driver_canal-82zqz_kube-system_65be83a6-2e7c-41ca-b585-74604d9532d3_0
767e2b68ba1f 4ab373b1fac4 “/opt/cni/bin/install” 7 minutes ago Exited (0) 7 minutes ago k8s_install-cni_canal-82zqz_kube-system_65be83a6-2e7c-41ca-b585-74604d9532d3_0
05fb9d8658d1 rancher/rke-tools:v0.1.66 “/docker-entrypoint.…” 14 minutes ago Up 14 minutes etcd-rolling-snapshots
2be6683e0cbf b5af743e5984 “/server” About an hour ago Up About an hour k8s_default-http-backend_default-http-backend-65dd5949d9-hk97d_ingress-nginx_0ea76324-eca4-438b-a4b0-2e871396e007_0
50882681c0ee 1f0ca6d99110 “/usr/bin/dumb-init …” About an hour ago Up About an hour k8s_nginx-ingress-controller_nginx-ingress-controller-ghwt4_ingress-nginx_c410838a-e506-4b4b-92c5-da7bf6817eb8_0
cbf741e0b5c8 rancher/pause:3.2 “/pause” About an hour ago Up About an hour k8s_POD_nginx-ingress-controller-ghwt4_ingress-nginx_c410838a-e506-4b4b-92c5-da7bf6817eb8_0
3029bb8ddec8 rancher/pause:3.2 “/pause” About an hour ago Up About an hour k8s_POD_default-http-backend-65dd5949d9-hk97d_ingress-nginx_0ea76324-eca4-438b-a4b0-2e871396e007_0
ea3e9693e727 rancher/metrics-server “/metrics-server --k…” About an hour ago Up About an hour k8s_metrics-server_metrics-server-8449844bf-xv9wg_kube-system_2645cae4-7297-417a-9bee-18fe16bec461_0
5795cf22121d rancher/pause:3.2 “/pause” About an hour ago Up About an hour k8s_POD_metrics-server-8449844bf-xv9wg_kube-system_2645cae4-7297-417a-9bee-18fe16bec461_0
c1a0b2b23923 bfe3a36ebd25 “/coredns -conf /etc…” About an hour ago Up About an hour k8s_coredns_coredns-6f85d5fb88-dbjhg_kube-system_86565788-ecb1-46c5-81ae-3fdfa6baf3f9_0
14d05b0dc36a 4f1064cf7caf “/cluster-proportion…” About an hour ago Up About an hour k8s_autoscaler_coredns-autoscaler-79599b9dc6-ssjsh_kube-system_a09fa1ac-b032-4ecc-b3c0-a48dda33e290_0
5914ef519bdd rancher/pause:3.2 “/pause” About an hour ago Up About an hour k8s_POD_coredns-6f85d5fb88-dbjhg_kube-system_86565788-ecb1-46c5-81ae-3fdfa6baf3f9_0
c76e775e4f66 rancher/pause:3.2 “/pause” About an hour ago Up About an hour k8s_POD_coredns-autoscaler-79599b9dc6-ssjsh_kube-system_a09fa1ac-b032-4ecc-b3c0-a48dda33e290_0
f8497b6f6c94 03feeb39a75a “/usr/bin/kube-contr…” About an hour ago Up About an hour k8s_calico-kube-controllers_calico-kube-controllers-649b7b795b-ff4wp_kube-system_46104a1a-afac-4399-91a5-52d370142664_0
e28066245c18 rancher/pause:3.2 “/pause” About an hour ago Up About an hour k8s_POD_calico-kube-controllers-649b7b795b-ff4wp_kube-system_46104a1a-afac-4399-91a5-52d370142664_1
8b46a0430b2c 0bfefe9f649b “/opt/bin/flanneld -…” About an hour ago Up About an hour k8s_kube-flannel_canal-82zqz_kube-system_65be83a6-2e7c-41ca-b585-74604d9532d3_0
278ae50517ae 0f351f210d5e “start_runit” About an hour ago Up About an hour k8s_calico-node_canal-82zqz_kube-system_65be83a6-2e7c-41ca-b585-74604d9532d3_0
549132d6480d rancher/pause:3.2 “/pause” About an hour ago Up About an hour k8s_POD_canal-82zqz_kube-system_65be83a6-2e7c-41ca-b585-74604d9532d3_0
45abd9919f2b rancher/hyperkube:v1.19.4-rancher1 “/opt/rke-tools/entr…” About an hour ago Up About an hour kube-proxy
67bcbcca715b rancher/hyperkube:v1.19.4-rancher1 “/opt/rke-tools/entr…” About an hour ago Up About an hour kubelet
91e2a0c5ad5b rancher/hyperkube:v1.19.4-rancher1 “/opt/rke-tools/entr…” About an hour ago Up About an hour kube-scheduler
d3d47eaa220c rancher/hyperkube:v1.19.4-rancher1 “/opt/rke-tools/entr…” About an hour ago Up About an hour kube-controller-manager
ed65da5f9bad rancher/hyperkube:v1.19.4-rancher1 “/opt/rke-tools/entr…” 2 hours ago Up 2 hours kube-apiserver
a9f5dd5d68f1 rancher/coreos-etcd:v3.4.13-rancher1 “/usr/local/bin/etcd…” 2 hours ago Up 2 hours etcd
Is this a healthy and successful installation?
Tried installing Rancher on top of this with Helm and default cert-manager, no errors were noticed during install. cert-manager components seem good no errors noticed. but when trying to access UI it throws an error default backend - 404.
Any guidance/help would be much appreciated.