すでに自己解決しました
分からないこと
kubernetesのdocument: Set up a High Availability etcd cluster with kubeadm通りにクラスタを構築しようとしたのですが、以下のようにapiserverが動きません。
NAMESPACE NAME READY STATUS RESTARTS AGE kube-system kube-apiserver1 0/1 CrashLoopBackOff 7 5s
Type Reason Age From Message ---- ------ ---- ---- ------- Warning Unhealthy 12m (x9 over 30m) kubelet, kube-apiserver1 Liveness probe failed: HTTP probe failed with statuscode: 500 Normal Killing 12m kubelet, kube-apiserver1 Container kube-apiserver failed liveness probe, will be restarted Warning Unhealthy 11m kubelet, kube-apiserver1 Liveness probe failed: Get https://192.168.33.11:6443/healthz: read tcp 192.168.33.11:55770->192.168.33.11:6443: read: connection reset by peer Warning Unhealthy 11m kubelet, kube-apiserver1 Liveness probe failed: Get https://192.168.33.11:6443/healthz: read tcp 192.168.33.11:55932->192.168.33.11:6443: read: connection reset by peer Normal Created 10m (x4 over 32m) kubelet, kube-apiserver1 Created container kube-apiserver Normal Started 10m (x4 over 32m) kubelet, kube-apiserver1 Started container kube-apiserver Warning Unhealthy 10m kubelet, kube-apiserver1 Liveness probe failed: Get https://192.168.33.11:6443/healthz: read tcp 192.168.33.11:56246->192.168.33.11:6443: read: connection reset by peer Normal Pulled 6m46s (x7 over 32m) kubelet, kube-apiserver1 Container image "k8s.gcr.io/kube-apiserver:v1.15.0" already present on machine Warning BackOff 100s (x38 over 10m) kubelet, kube-apiserver1 Back-off restarting failed container
回答1件
あなたの回答
tips
プレビュー
バッドをするには、ログインかつ
こちらの条件を満たす必要があります。