Kubeadm: Kubeadm init memblokir di "Ini mungkin memakan waktu satu menit atau lebih lama jika gambar bidang kontrol harus ditarik

Dibuat pada 31 Jan 2018 · 67Komentar · Sumber: kubernetes/kubeadm

Versi

versi kubeadm (gunakan kubeadm version ):

Lingkungan :

Versi Kubernetes (gunakan kubectl version ):v1.9.2
Penyedia cloud atau konfigurasi perangkat keras : Kotak Virtual
OS (misalnya dari /etc/os-release): Ubuntu 16.04.0 LTS (Xeniak Xerus) amd64
Kernel (misalnya uname -a ):linux 4.4.0-62-generic
Lainnya : versi kubeadm :v1.9.2: amd64, versi kubelet :v1.9.2 amd64, versi kubernetes-cni :0.6.-00 amd64 , versi docker:17.03.2-ce

Apa yang terjadi?

Saat saya mencoba menjalankan kubeadm init, itu hang dengan
xx@xx :~$ sudo kubeadm init --kubernetes-version=v1.9.2

[init] Menggunakan versi Kubernetes: v1.9.2
[init] Menggunakan mode Otorisasi: [Node RBAC]
[preflight] Menjalankan pemeriksaan pra-penerbangan.
[PERINGATAN FileExisting-crictl]: crictl tidak ditemukan di jalur sistem
[preflight] Memulai layanan kubelet
[sertifikat] Sertifikat dan kunci ca yang dihasilkan.
[sertifikat] Sertifikat dan kunci apiserver yang dihasilkan.
[sertifikat] sertifikat penyajian apiserver ditandatangani untuk nama DNS [kickseed kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] dan IP [10.96.0.1 172.17.41.15]
[sertifikat] Membuat sertifikat dan kunci apiserver-kubelet-client.
[sertifikat] Dihasilkan sa kunci dan kunci publik.
[sertifikat] Sertifikat dan kunci front-proxy-ca yang dihasilkan.
[sertifikat] Sertifikat dan kunci klien-proksi-depan yang dibuat.
[sertifikat] Sertifikat dan kunci yang valid sekarang ada di "/etc/kubernetes/pki"
[kubeconfig] Tulis file KubeConfig ke disk: "admin.conf"
[kubeconfig] Tulis file KubeConfig ke disk: "kubelet.conf"
[kubeconfig] Tulis file KubeConfig ke disk: "controller-manager.conf"
[kubeconfig] Tulis file KubeConfig ke disk: "scheduler.conf"
[controlplane] Tulis manifes Pod Statis untuk komponen kube-apiserver ke "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] Menulis manifes Pod Statis untuk komponen kube-controller-manager ke "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] Menulis manifes Pod Statis untuk komponen kube-scheduler ke "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Tulis manifes Pod Statis untuk instance etcd lokal ke "/etc/kubernetes/manifests/etcd.yaml"
[init] Menunggu kubelet mem-boot control plane sebagai Static Pods dari direktori "/etc/kubernetes/manifests".
[init] Ini mungkin memakan waktu satu menit atau lebih lama jika gambar bidang kontrol harus ditarik.

Kemudian saya memeriksa log kubelet:
xx@xx :~$ sudo journalctl -xeu kubelet:
31 Jan 14:45:03 kickseed kubelet[28516]: E0131 14:45:03.280984 28516 remote_runtime.go:92] RunPodSandbox dari layanan runtime gagal: rpc error: code = Unknown desc = gagal menarik gambar "gcr.io/google_containers/ pause-AMD64:3.0": Respons kesalahan dari daemon: Dapatkan https://gcr.io/v1/_ping : dial tcp 172.217.6.127:443: i/o timeout
Jan 31 14:45:03 kickseed kubelet[28516]: E0131 14:45:03.281317 28516 kuberuntime_sandbox.go:54] CreatePodSandbox untuk pod "kube-scheduler-kickseed_kube-system(69c12074e336b0dbbd0a1666ce05226ce error = rpa error)" = gagal menarik gambar "gcr.io/google_containers/pause-amd64:3.0": Respons kesalahan dari daemon: Dapatkan https://gcr.io/v1/_ping : dial tcp 172.217.6.127:443: i/o timeout
Jan 31 14:45:03 kickseed kubelet[28516]: E0131 14:45:03.281580 28516 kuberuntime_manager.go:647] createPodSandbox untuk pod "kube-scheduler-kickseed_kube-system(69c12074e336b0dbbd0a1666ce05226c error = Unknown de: rpa error = rpa error)" = gagal menarik gambar "gcr.io/google_containers/pause-amd64:3.0": Respons kesalahan dari daemon: Dapatkan https://gcr.io/v1/_ping : dial tcp 172.217.6.127:443: i/o timeout
31 Jan 14:45:03 kickseed kubelet[28516]: E0131 14:45:03.281875 28516 pod_workers.go:186] Kesalahan saat menyinkronkan pod 69c12074e336b0dbbd0a1666ce05226a ("kube-scheduler-kickseed_kube-system(69c12074e336b)dbbbd skipping:" CreatePodSandbox" untuk "kube-scheduler-kickseed_kube-system(69c12074e336b0dbbd0a1666ce05226a)" dengan CreatePodSandboxError: "CreatePodSandbox untuk pod \"kube-scheduler-kickseed_kube-system(69c12074e336b) kode menarik gambar gagal "gcr.io/google_containers/pause-amd64:3.0\": Respons kesalahan dari daemon: Dapatkan https://gcr.io/v1/_ping : tekan tcp 172.217.6.127:443: i/o timeout"
31 Jan 14:45:03 kickseed kubelet[28516]: E0131 14:45:03.380290 28516 event.go:209] Tidak dapat menulis acara: 'Patch https://172.17.41.15 :6443/api/v1/namespaces/default /events/kickseed.150ecf46afb098b7: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak' (dapat mencoba lagi setelah tidur)
31 Jan 14:45:03 kickseed kubelet[28516]: E0131 14:45:03.933783 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Gagal membuat daftar *v1. Pod: Dapatkan https://172.17.41.15 :6443/api/v1/pods?fieldSelector=spec.nodeName%3Dkickseed&limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:45:03 kickseed kubelet[28516]: E0131 14:45:03.934707 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Gagal membuat daftar *v1.Node: Dapatkan https://172.17.41.15 :6443/api/v1/nodes?fieldSelector=metadata.name%3Dkickseed&limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
Jan 31 14:45:03 kickseed kubelet[28516]: E0131 14:45:03.935921 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Gagal mendaftar *v1.Service: Dapatkan https://172.17.41.15 :6443/api/v1/services?limit=500&resourceVersion=0: panggil tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:45:04 kickseed kubelet[28516]: E0131 14:45:04.281024 28516 remote_runtime.go:92] RunPodSandbox dari layanan runtime gagal: rpc error: code = Unknown desc = gagal menarik gambar "gcr.io/google_containers/ pause-AMD64:3.0": Respons kesalahan dari daemon: Dapatkan https://gcr.io/v1/_ping : dial tcp 172.217.6.127:443: i/o timeout
31 Jan 14:45:04 kickseed kubelet[28516]: E0131 14:45:04.281352 28516 kuberuntime_sandbox.go:54] CreatePodSandbox untuk pod "kube-controller-manager-kickseed_kube-system(6546d6faf0b50c9fc6712ce25ee9b6cb25ee9b) Unknown desc = gagal menarik gambar "gcr.io/google_containers/pause-amd64:3.0": Respons kesalahan dari daemon: Dapatkan https://gcr.io/v1/_ping : dial tcp 172.217.6.127:443: i/o timeout
31 Jan 14:45:04 kickseed kubelet[28516]: E0131 14:45:04.281634 28516 kuberuntime_manager.go:647] createPodSandbox untuk pod "kube-controller-manager-kickseed_kube-system(6546d6faf0b50c9fc6712ce25ee9b6cb25ee9b) Unknown desc = gagal menarik gambar "gcr.io/google_containers/pause-amd64:3.0": Respons kesalahan dari daemon: Dapatkan https://gcr.io/v1/_ping : dial tcp 172.217.6.127:443: i/o timeout
31 Jan 14:45:04 kickseed kubelet[28516]: E0131 14:45:04.281938 28516 pod_workers.go:186] Kesalahan saat menyinkronkan pod 6546d6faf0b50c9fc6712ce25ee9b6cb ("kube-controller-manager-kickseed_kube-system") f06bc50c69fc67b50c69 Hapus "CreatePodSandbox" untuk "kube-controller-manager-kickseed_kube-system(6546d6faf0b50c9fc6712ce25ee9b6cb)" dengan CreatePodSandboxError: "CreatePodSandbox untuk pod \"kube-controller-manager-kickseed_kube-system" desc = gagal menarik gambar \"gcr.io/google_containers/pause-amd64:3.0\": Tanggapan kesalahan dari daemon: Dapatkan https://gcr.io/v1/_ping : dial tcp 172.217.6.127:443: i/o waktu habis"
31 Jan 14:45:04 kickseed kubelet[28516]: E0131 14:45:04.934694 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Gagal membuat daftar *v1. Pod: Dapatkan https://172.17.41.15 :6443/api/v1/pods?fieldSelector=spec.nodeName%3Dkickseed&limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:45:04 kickseed kubelet[28516]: E0131 14:45:04.935613 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Gagal mendaftar *v1.Node: Dapatkan https://172.17.41.15 :6443/api/v1/nodes?fieldSelector=metadata.name%3Dkickseed&limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:45:04 kickseed kubelet[28516]: E0131 14:45:04.936669 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Gagal membuat daftar *v1.Layanan: Dapatkan https://172.17.41.15 :6443/api/v1/services?limit=500&resourceVersion=0: panggil tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:45:05 kickseed kubelet[28516]: W0131 14:45:05.073692 28516 cni.go:171] Tidak dapat memperbarui konfigurasi cni: Tidak ada jaringan yang ditemukan di /etc/cni/net.d
31 Jan 14:45:05 kickseed kubelet[28516]: E0131 14:45:05.074106 28516 kubelet.go:2105] Jaringan runtime container tidak siap: NetworkReady= alasan salah:NetworkPluginNotReady pesan:docker : plugin jaringan belum siap: cni config tidak diinisialisasi
31 Jan 14:45:05 kickseed kubelet[28516]: E0131 14:45:05.935680 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Gagal membuat daftar *v1. Pod: Dapatkan https://172.17.41.15 :6443/api/v1/pods?fieldSelector=spec.nodeName%3Dkickseed&limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:45:05 kickseed kubelet[28516]: E0131 14:45:05.937423 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Gagal mendaftar *v1.Node: Dapatkan https://172.17.41.15 :6443/api/v1/nodes?fieldSelector=metadata.name%3Dkickseed&limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:45:05 kickseed kubelet[28516]: E0131 14:45:05.937963 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Gagal mendaftar *v1.Layanan: Dapatkan https://172.17.41.15 :6443/api/v1/services?limit=500&resourceVersion=0: panggil tcp 172.17.41.15:6443: getockopt: koneksi ditolak
Jan 31 14:45:05 kickseed kubelet[28516]: I0131 14:45:05.974034 28516 kubelet_node_status.go:273] Menyetel anotasi simpul untuk mengaktifkan pengontrol volume pasang/lepas
Jan 31 14:45:06 kickseed kubelet[28516]: I0131 14:45:06.802447 28516 kubelet_node_status.go:273] Mengatur anotasi simpul untuk mengaktifkan pengontrol volume pasang/lepas
Jan 31 14:45:06 kickseed kubelet[28516]: I0131 14:45:06.804242 28516 kubelet_node_status.go:82] Mencoba mendaftarkan node kickseed
31 Jan 14:45:06 kickseed kubelet[28516]: E0131 14:45:06.804778 28516 kubelet_node_status.go:106] Tidak dapat mendaftarkan node "kickseed" dengan server API: Posting https://172.17.41.15 :6443/api/ v1/node: tekan tcp 172.17.41.15:6443: getockopt: con

xx@xx :~$ sudo systemctl status kubelet:

kubelet.service - kubelet: Agen Node Kubernetes
Dimuat: dimuat (/lib/systemd/system/kubelet.service; diaktifkan; preset vendor: diaktifkan)
Drop-In: /etc/systemd/system/kubelet.service.d
11-kubeadm.conf, 10-kubeadm1.conf, 90-local-extras.conf
Aktif: aktif (berjalan) sejak Rabu-31-01-2018 13:53:46 CST; 49 menit yang lalu
Dokumen: http://kubernetes.io/docs/
PID Utama: 28516 (kubelet)
Tugas: 13
Memori: 37.8M
CPU: 22.767 detik
CGroup: /system.slice/kubelet.service
28516 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --pod-manifest-path=/etc/kubernetes/ memanifestasikan --allow-privileged=true --cgroup-driver=cgroupfs --network-plugin=cni --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni /bin --cluster-dns=10.96.0.10 --cluster-domain=cluster.local --authorization-mode=Webhook --client-ca-file=/etc/kubernetes/pki/ca.crt --cadvisor-port =0 --rotate-certificates=true --cert-dir=/var/lib/kubelet/pki --fail-swap-on=false

31 Jan 14:43:17 kickseed kubelet[28516]: E0131 14:43:17.862590 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Gagal membuat daftar *v1.Node: Dapatkan https://172.17.41.15 :6443/api/v1/nodes?fieldSelector=metadata.name%3Dkickseed&limit=500&resourceVersion=0: dial tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:43:17 kickseed kubelet[28516]: E0131 14:43:17.863474 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Gagal membuat daftar *v1.Layanan: Dapatkan https://172.17.41.15 :6443/api/v1/services?limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:43:18 kickseed kubelet[28516]: E0131 14:43:18.621818 28516 event.go:209] Tidak dapat menulis acara: 'Patch https://172.17.41.15 :6443/api/v1/namespaces/default /events/kickseed.150ecf46afb098b7: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak' (dapat mencoba lagi setelah tidur)
31 Jan 14:43:18 kickseed kubelet[28516]: E0131 14:43:18.862440 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Gagal membuat daftar *v1. Pod: Dapatkan https://172.17.41.15 :6443/api/v1/pods?fieldSelector=spec.nodeName%3Dkickseed&limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:43:18 kickseed kubelet[28516]: E0131 14:43:18.863379 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Gagal membuat daftar *v1.Node: Dapatkan https://172.17.41.15 :6443/api/v1/nodes?fieldSelector=metadata.name%3Dkickseed&limit=500&resourceVersion=0: dial tcp 172.17.41.15:6443: getockopt: koneksi ditolak
Jan 31 14:43:18 kickseed kubelet[28516]: E0131 14:43:18.864424 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Gagal membuat daftar *v1.Service: Dapatkan https://172.17.41.15 :6443/api/v1/services?limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:43:19 kickseed kubelet[28516]: E0131 14:43:19.255460 28516 eviction_manager.go:238] eviction manager: tak terduga err: gagal mendapatkan info simpul: simpul "kickseed" tidak ditemukan
31 Jan 14:43:19 kickseed kubelet[28516]: E0131 14:43:19.863266 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Gagal membuat daftar *v1. Pod: Dapatkan https://172.17.41.15 :6443/api/v1/pods?fieldSelector=spec.nodeName%3Dkickseed&limit=500&resourceVersion=0: tekan tcp 172.17.41.15:6443: getockopt: koneksi ditolak
31 Jan 14:43:19 kickseed kubelet[28516]: E0131 14:43:19.864238 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Gagal membuat daftar *v1.Node: Dapatkan https://172.17.41.15 :6443/api/v1/nodes?fieldSelector=metadata.name%3Dkickseed&limit=500&resourceVersion=0: dial tcp 172.17.41.15:6443: getockopt: koneksi ditolak
Jan 31 14:43:19 kickseed kubelet[28516]: E0131 14:43:19.865262 28516 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:465: Gagal mendaftar *v1.Service: Dapatkan https://172.17.41.15 :6443/api/v1/services?limit=500&resourceVersion=0: dial tcp 172.17.41.15:6443: getockopt: koneksi ditolak

Beberapa gambar buruh pelabuhan terdaftar sebagai berikut:
gcr.io/google_containers/kube-apiserver-amd64:v1.9.2
gcr.io/google_containers/kube-controller-manager-amd64:v1.9.2
gcr.io/google_containers/kube-scheduler-amd64:v1.9.2
gcr.io/google_containers/kube-proxy-amd64:v1.9.2
gcr.io/google_containers/etcd-amd64:3.2.14
gcr.io/google_containers/pause-amd64:3.1
gcr.io/google_containers/kube-dnsmasq-amd64:1.4.1
gcr.io/google_containers/kubernetes-dashboard-amd64:v1.8.2
gcr.io/google_containers/kubedns-amd64:1.9
gcr.io/google_containers/kube-discovery-amd64:1.0
gcr.io/google_containers/exechealthz-amd64:v1.2.0
gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.8
gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.8
gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.8
gcr.io/google_containers/dnsmasq-metrics-amd64:1.0.1

Apa yang Anda harapkan terjadi?

kubeadm init harus selesai

Bagaimana cara mereproduksinya (seminimal dan setepat mungkin)?

virtualbox dengan Ubuntu 16.04 dan kubeadm 1.9.2

Ada lagi yang perlu kita ketahui?

areUX lifecyclactive prioritimportant-soon

Sumber

PhoenixAD

👍12

Komentar yang paling membantu

https://github.com/kubernetes/kubernetes/issues/59680#issuecomment -364646304
menonaktifkan selinux membantu saya.

avielb pada 19 Mar 2018

😕7 👍7 👎6 🎉2 ❤1

Semua 67 komentar

Gambar buruh pelabuhan yang tercantum di atas diambil dari repositori pribadi saya sebelum menjalankan "kubeadm init --kubernetes-version v1.9.2" , saya tidak dapat langsung mengakses gcr.io/google-containers karena GFW.

PhoenixAD pada 31 Jan 2018

Masalah yang sama disini!

hedinasr pada 6 Feb 2018

Saya memiliki masalah yang sama pada CentOS 7

6l20 pada 7 Feb 2018

fluidjeel pada 8 Feb 2018

newhomie pada 9 Feb 2018

tmilleville pada 9 Feb 2018

+1
server di vultr, terjebak di sini juga.

WindGreen pada 9 Feb 2018

grantcurell pada 9 Feb 2018

humorcode pada 12 Feb 2018

CFAndy pada 12 Feb 2018

Sebagai solusi

1/ buat registri buruh pelabuhan di master kubernetes Anda

2/ nyatakan master kubernetes Anda sebagai gcr.io di /etc/hosts

3/ Pada mesin dengan akses internet, masuk ke ggogle cloud dan unduh gambar
contoh:
gloud docker -- tarik gcrio/goole_container/pause-AMD64:3.0
gloud docker -- simpan -o /tmp/pause-amd.tar gcrio/goole_container/pause-amd64:3.0

4/ Unggah gambar ke register repo buruh pelabuhan
beban buruh pelabuhan -i /tmp/pause-amd64.tar
tag buruh pelabuhan gcr.io/Google_containers/pause-amd64:3.0 yourdoke rregistry:pause-amd64 :3.0
Docker Docker Registry Doke Anda: Pause-AMD64 :3.0

5/ Pada master kebernetes Anda sebagai gcr.io docker registry

Dapatkan gambar dari repo registri buruh pelabuhan Anda
buruh pelabuhan tarik registry dok Anda: jeda-amd64 :3.0

Tarik ke registri buruh pelabuhan gcr.io lokal Anda
tandai docker registrasi dok Anda: jeda-amd64 :3.0 gcr.io/google_containers/pause-amd64:3.0
docker push gcr.io/google_containers/pause-amd64:3.0

Unduh semua gambar yang digunakan oleh kubeadm init . Lihat di /etc/kubernetes/manifest/*.yaml

tmilleville pada 12 Feb 2018

👎31 👍1

Apakah sudah diperbaiki di 1.9.3?

alexpekurovsky pada 16 Feb 2018

edwardofclt pada 23 Feb 2018

+1 - Ini hanya memanifestasikan kedua kalinya saya menjalankan kubeadm init. Pertama kali tendangan melalui baik-baik saja. Saya tidak yakin apakah ada sedikit status dari run pertama yang tidak dibersihkan dengan benar dengan reset kubeadm.

patrickstjohn pada 25 Feb 2018

emisty pada 27 Feb 2018

centos 7 dan saya mengatur proxy di /etc/env lalu tampilkan sebagai

emisty pada 27 Feb 2018

😕1

simis2626 pada 28 Feb 2018

Masalah yang sama disini. Centos7, kube install terbaru (1.9.3), mencoba dokumentasi hightower, dan semua dokumentasi kubernetes. etcd dan flanel bekerja dan hidup dan naik. Menggunakan variabel env NO_PROXY untuk memasukkan IP eksternal saya sehingga tidak akan mencoba koneksi proxy ke koneksi lain, namun tidak pernah benar-benar mencapai titik itu, dan mendapatkan kesalahan yang sama seperti orang lain di atas.

multipathmaster pada 28 Feb 2018

robertBrem pada 2 Mar 2018

Saya memiliki masalah yang sama, centos 7, kubelet v1.9.3;
Tapi sepertinya gambar-gambar itu berhasil diunduh,
docker images
gcr.io/google_containers/kube-apiserver-amd64 v1.9.3 360d55f91cbf 4 weeks ago 210.5 MB gcr.io/google_containers/kube-controller-manager-amd64 v1.9.3 83dbda6ee810 4 weeks ago 137.8 MB gcr.io/google_containers/kube-scheduler-amd64 v1.9.3 d3534b539b76 4 weeks ago 62.71 MB gcr.io/google_containers/etcd-amd64 3.1.11 59d36f27cceb 3 months ago 193.9 MB gcr.io/google_containers/pause-amd64 3.0 99e59f495ffa 22 months ago 746.9 kB

wangsenyuan pada 8 Mar 2018

❤1

Saya memiliki CentOS 7 vm di sini, dan sudah mengonfigurasinya dengan server proxy kami.
Saya mendapat pesan time out yang sama, tetapi gambar buruh pelabuhan telah ditarik dan aktif dan berjalan.

mvsouza pada 8 Mar 2018

Saya juga, mengalami masalah yang sama. Lihat output dan log untuk informasi lebih lanjut.

```[ root@kube01 ~]# kubeadm init
[init] Menggunakan versi Kubernetes: v1.9.3
[init] Menggunakan mode Otorisasi: [Node RBAC]
[preflight] Menjalankan pemeriksaan pra-penerbangan.
[Nama Host PERINGATAN]: nama host "kube01" tidak dapat dihubungi
[PERINGATAN Hostname]: nama host "kube01" mencari kube01 pada 10.10.0.81:53: server mengalami gangguan
[PERINGATAN FileExisting-crictl]: crictl tidak ditemukan di jalur sistem
[preflight] Memulai layanan kubelet
[sertifikat] Sertifikat dan kunci ca yang dihasilkan.
[sertifikat] Sertifikat dan kunci apiserver yang dihasilkan.
[sertifikat] sertifikat penyajian apiserver ditandatangani untuk nama DNS [kube01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] dan IP [10.96.0.1 10.25.123.11]
[sertifikat] Membuat sertifikat dan kunci apiserver-kubelet-client.
[sertifikat] Dihasilkan sa kunci dan kunci publik.
[sertifikat] Sertifikat dan kunci front-proxy-ca yang dihasilkan.
[sertifikat] Sertifikat dan kunci klien-proksi-depan yang dibuat.
[sertifikat] Sertifikat dan kunci yang valid sekarang ada di "/etc/kubernetes/pki"
[kubeconfig] Tulis file KubeConfig ke disk: "admin.conf"
[kubeconfig] Tulis file KubeConfig ke disk: "kubelet.conf"
[kubeconfig] Tulis file KubeConfig ke disk: "controller-manager.conf"
[kubeconfig] Tulis file KubeConfig ke disk: "scheduler.conf"
[controlplane] Tulis manifes Pod Statis untuk komponen kube-apiserver ke "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] Menulis manifes Pod Statis untuk komponen kube-controller-manager ke "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] Menulis manifes Pod Statis untuk komponen kube-scheduler ke "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Tulis manifes Pod Statis untuk instance etcd lokal ke "/etc/kubernetes/manifests/etcd.yaml"
[init] Menunggu kubelet mem-boot control plane sebagai Static Pods dari direktori "/etc/kubernetes/manifests".
[init] Ini mungkin memakan waktu satu menit atau lebih lama jika gambar bidang kontrol harus ditarik.

In the meantime, while watching `docker ps` this is what I see:
***Note:*** Don't mind the length of time that the containers have been up — this is my third attempt and it's always the same.

```CONTAINER ID        IMAGE
              COMMAND                  CREATED              STATUS              PORTS               NAMES
c422b3fd67f9        gcr.io/google_containers/kube-apiserver-amd64<strong i="5">@sha256</strong>:a5382344aa373a90bc87d3baa4eda5402507e8df5b8bfbbad392c4fff715f0
43            "kube-apiserver --req"   About a minute ago   Up About a minute                       k8s_kube-apiserver_kube-apiserver-k
ube01_kube-system_3ff6faac27328cf290a026c08ae0ce75_1
4b30b98bcc24        gcr.io/google_containers/kube-controller-manager-amd64<strong i="6">@sha256</strong>:3ac295ae3e78af5c9f88164ae95097c2d7af03caddf067cb35599
769d0b7251e   "kube-controller-mana"   2 minutes ago        Up 2 minutes                            k8s_kube-controller-manager_kube-co
ntroller-manager-kube01_kube-system_d556d9b8ccdd523a5208b391ca206031_0
71c6505ed125        gcr.io/google_containers/kube-scheduler-amd64<strong i="7">@sha256</strong>:2c17e637c8e4f9202300bd5fc26bc98a7099f49559ca0a8921cf692ffd4a16
75            "kube-scheduler --add"   2 minutes ago        Up 2 minutes                            k8s_kube-scheduler_kube-scheduler-k
ube01_kube-system_6502dddc08d519eb6bbacb5131ad90d0_0
9d01e2de4686        gcr.io/google_containers/pause-amd64:3.0
              "/pause"                 3 minutes ago        Up 2 minutes                            k8s_POD_kube-controller-manager-kub
e01_kube-system_d556d9b8ccdd523a5208b391ca206031_0
7fdaabc7e2a7        gcr.io/google_containers/pause-amd64:3.0
              "/pause"                 3 minutes ago        Up 2 minutes                            k8s_POD_kube-apiserver-kube01_kube-
system_3ff6faac27328cf290a026c08ae0ce75_0
a5a2736e6cd0        gcr.io/google_containers/pause-amd64:3.0
              "/pause"                 3 minutes ago        Up 2 minutes                            k8s_POD_kube-scheduler-kube01_kube-
system_6502dddc08d519eb6bbacb5131ad90d0_0
ea82cd3a27da        gcr.io/google_containers/pause-amd64:3.0
              "/pause"                 3 minutes ago        Up 2 minutes                            k8s_POD_etcd-kube01_kube-system_727
8f85057e8bf5cb81c9f96d3b25320_0

KELUARAN LOG UNTUK gcr.io/google_containers/ kube-apiserver-amd64@sha256 :a5382344aa373a90bc87d3baa4eda5402507e8df5b8bfbbad392c4fff715f043

I0309 19:59:29.570990       1 server.go:121] Version: v1.9.3
I0309 19:59:29.756611       1 feature_gate.go:190] feature gates: map[Initializers:true]
I0309 19:59:29.756680       1 initialization.go:90] enabled Initializers feature as part of admission plugin setup
I0309 19:59:29.760396       1 master.go:225] Using reconciler: master-count
W0309 19:59:29.789648       1 genericapiserver.go:342] Skipping API batch/v2alpha1 because it has no resources.
W0309 19:59:29.796731       1 genericapiserver.go:342] Skipping API rbac.authorization.k8s.io/v1alpha1 because it has no resources.
W0309 19:59:29.797445       1 genericapiserver.go:342] Skipping API storage.k8s.io/v1alpha1 because it has no resources.
W0309 19:59:29.804841       1 genericapiserver.go:342] Skipping API admissionregistration.k8s.io/v1alpha1 because it has no resources.
[restful] 2018/03/09 19:59:29 log.go:33: [restful/swagger] listing is available at https://10.25.123.11:6443/swaggerapi
[restful] 2018/03/09 19:59:29 log.go:33: [restful/swagger] https://10.25.123.11:6443/swaggerui/ is mapped to folder /swagger-ui/
[restful] 2018/03/09 19:59:30 log.go:33: [restful/swagger] listing is available at https://10.25.123.11:6443/swaggerapi
[restful] 2018/03/09 19:59:30 log.go:33: [restful/swagger] https://10.25.123.11:6443/swaggerui/ is mapped to folder /swagger-ui/
I0309 19:59:32.393800       1 serve.go:89] Serving securely on [::]:6443
I0309 19:59:32.393854       1 apiservice_controller.go:112] Starting APIServiceRegistrationController
I0309 19:59:32.393866       1 cache.go:32] Waiting for caches to sync for APIServiceRegistrationController controller
I0309 19:59:32.393965       1 controller.go:84] Starting OpenAPI AggregationController
I0309 19:59:32.393998       1 crdregistration_controller.go:110] Starting crd-autoregister controller
I0309 19:59:32.394012       1 controller_utils.go:1019] Waiting for caches to sync for crd-autoregister controller
I0309 19:59:32.394034       1 customresource_discovery_controller.go:152] Starting DiscoveryController
I0309 19:59:32.394057       1 naming_controller.go:274] Starting NamingConditionController
I0309 19:59:32.393855       1 crd_finalizer.go:242] Starting CRDFinalizer
I0309 19:59:32.394786       1 available_controller.go:262] Starting AvailableConditionController
I0309 19:59:32.394815       1 cache.go:32] Waiting for caches to sync for AvailableConditionController controller
I0309 20:00:06.434318       1 trace.go:76] Trace[12318713]: "Create /api/v1/nodes" (started: 2018-03-09 19:59:32.431463052 +0000 UTC m=+2.986431803) (total time: 34.002792758s):
Trace[12318713]: [4.00201898s] [4.001725343s] About to store object in database
Trace[12318713]: [34.002792758s] [30.000773778s] END
E0309 20:00:32.406206       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.LimitRange: the server was unable to return a response in the time allotted, but may still be processing the request (get limitranges)
E0309 20:00:32.406339       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.Secret: the server was unable to return a response in the time allotted, but may still be processing the request (get secrets)
E0309 20:00:32.406342       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/kube-aggregator/pkg/client/informers/internalversion/factory.go:73: Failed to list *apiregistration.APIService: the server was unable to return a response in the time allotted, but may still be processing the request (get apiservices.apiregistration.k8s.io)
E0309 20:00:32.408094       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.Pod: the server was unable to return a response in the time allotted, but may still be processing the request (get pods)
E0309 20:00:32.415692       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.PersistentVolume: the server was unable to return a response in the time allotted, but may still be processing the request (get persistentvolumes)
E0309 20:00:32.415818       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/apiextensions-apiserver/pkg/client/informers/internalversion/factory.go:73: Failed to list *apiextensions.CustomResourceDefinition: the server was unable to return a response in the time allotted, but may still be processing the request (get customresourcedefinitions.apiextensions.k8s.io)
E0309 20:00:32.415862       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *rbac.ClusterRoleBinding: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterrolebindings.rbac.authorization.k8s.io)
E0309 20:00:32.415946       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Namespace: the server was unable to return a response in the time allotted, but may still be processing the request (get namespaces)
E0309 20:00:32.416029       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.ResourceQuota: the server was unable to return a response in the time allotted, but may still be processing the request (get resourcequotas)
E0309 20:00:32.416609       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *rbac.ClusterRole: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterroles.rbac.authorization.k8s.io)
E0309 20:00:32.416684       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *rbac.RoleBinding: the server was unable to return a response in the time allotted, but may still be processing the request (get rolebindings.rbac.authorization.k8s.io)
E0309 20:00:32.420305       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Endpoints: the server was unable to return a response in the time allotted, but may still be processing the request (get endpoints)
E0309 20:00:32.440196       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *storage.StorageClass: the server was unable to return a response in the time allotted, but may still be processing the request (get storageclasses.storage.k8s.io)
E0309 20:00:32.440403       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: the server was unable to return a response in the time allotted, but may still be processing the request (get services)
E0309 20:00:32.448018       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *core.ServiceAccount: the server was unable to return a response in the time allotted, but may still be processing the request (get serviceaccounts)
E0309 20:00:32.448376       1 reflector.go:205] k8s.io/kubernetes/pkg/client/informers/informers_generated/internalversion/factory.go:85: Failed to list *rbac.Role: the server was unable to return a response in the time allotted, but may still be processing the request (get roles.rbac.authorization.k8s.io)
E0309 20:00:33.395988       1 storage_rbac.go:175] unable to initialize clusterroles: the server was unable to return a response in the time allotted, but may still be processing the request (get clusterroles.rbac.authorization.k8s.io)
I0309 20:00:43.455564       1 trace.go:76] Trace[375160879]: "Create /api/v1/nodes" (started: 2018-03-09 20:00:13.454506587 +0000 UTC m=+44.009475397) (total time: 30.001008377s):
Trace[375160879]: [30.001008377s] [30.000778516s] END

================================================== ======================

KELUARAN LOG UNTUK gcr.io/google_containers/ kube-controller-manager-amd64@sha256 :3ac295ae3e78af5c9f88164ae95097c2d7af03caddf067cb35599769d0b7251e

I0309 19:51:35.248083       1 controllermanager.go:108] Version: v1.9.3
I0309 19:51:35.257251       1 leaderelection.go:174] attempting to acquire leader lease...
E0309 19:51:38.310839       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:51:41.766358       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:51:46.025824       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:51:49.622916       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:51:52.675648       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:51:55.697734       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:51:59.348765       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:01.508487       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:03.886473       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:06.120356       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:08.844772       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:12.083789       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:16.038882       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:18.555388       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:21.471034       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:24.236724       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:27.363968       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:30.045776       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:32.751626       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:36.383923       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:38.910958       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:41.400748       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:44.268909       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:47.640891       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:51.713420       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:54.419154       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:52:57.134430       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:00.942903       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:03.440586       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:07.518362       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:53:12.968927       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:16.228760       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:18.299005       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:20.681915       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:24.141874       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:28.484775       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:30.678092       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:34.107654       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:36.251647       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:39.914756       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:42.641017       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:45.058876       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:48.359511       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:51.667554       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:54.338101       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:53:57.357894       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:00.633504       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:03.244353       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:05.923510       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:09.817627       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:12.688349       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:16.803954       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:19.519269       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:23.668226       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:25.903217       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:54:30.248639       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:54:32.428029       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:54:34.962675       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:54:38.598370       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:54:41.179039       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:54:43.927574       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:54:48.190961       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:51.974141       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:55.898687       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:54:59.653210       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:02.094737       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:05.125275       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:09.280324       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:12.920886       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:17.272605       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:21.488182       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:23.708198       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:26.893696       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:31.121014       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:35.414628       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:38.252001       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:41.912479       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:45.621133       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:48.976244       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:52.537317       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:55.863737       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:55:59.682009       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:02.653432       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:04.968939       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:09.336478       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:56:13.488850       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:56:16.262967       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:56:22.685928       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:26.235497       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:28.442915       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:32.051827       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:35.547277       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:38.437120       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:41.007877       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:44.295081       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:46.746424       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:49.321870       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:52.831866       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:55.138333       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:56:57.815491       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:00.802112       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:03.848363       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:07.350593       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:10.672982       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:14.171660       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:17.923995       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:21.919624       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:23.923165       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:27.692006       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:30.654447       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:33.851703       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:57:37.302382       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:57:40.286552       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:57:42.358940       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:57:44.364982       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:57:46.372569       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:57:50.571683       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:57:53.988093       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:57:57.648006       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:01.607961       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:05.717138       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:08.819600       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:12.262314       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:14.327626       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:18.359683       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:20.961212       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:24.503457       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:27.099581       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:29.518623       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:32.943210       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:36.900236       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:40.567479       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:42.642410       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:45.938839       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:50.282483       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:54.086558       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:58:56.794469       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:00.604370       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:02.968978       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:05.825551       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:09.824458       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:12.383249       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:15.891164       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:59:19.088375       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:59:21.305063       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:59:23.366258       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:59:26.308481       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: Get https://10.25.123.11:6443/api/v1/namespaces/kube-system/endpoints/kube-controller-manager: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:59:32.440045       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:36.673744       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:40.049109       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:43.463730       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:46.454431       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:49.782639       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:52.964468       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 19:59:57.265527       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:01.181219       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:03.441468       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:07.324053       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:10.269835       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:12.584906       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:15.042928       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:18.820764       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:22.392476       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:24.630702       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:27.881904       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:30.123513       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:32.490088       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:34.675420       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:37.433904       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:39.819475       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"
E0309 20:00:42.152164       1 leaderelection.go:224] error retrieving resource lock kube-system/kube-controller-manager: endpoints "kube-controller-manager" is forbidden: User "system:kube-controller-manager" cannot get endpoints in the namespace "kube-system"

================================================== ======================

KELUARAN LOG UNTUK gcr.io/google_containers/ kube-scheduler-amd64@sha256 :2c17e637c8e4f9202300bd5fc26bc98a7099f49559ca0a8921cf692ffd4a1675

W0309 19:51:34.800737       1 server.go:159] WARNING: all flags than --config are deprecated. Please begin using a config file ASAP.
I0309 19:51:34.812848       1 server.go:551] Version: v1.9.3
I0309 19:51:34.817093       1 server.go:570] starting healthz server on 127.0.0.1:10251
E0309 19:51:34.818028       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.PodDisruptionBudget: Get https://10.25.123.11:6443/apis/policy/v1beta1/poddisruptionbudgets?limit=500&resourceVersion=0: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:51:34.818279       1 reflector.go:205] k8s.io/kubernetes/plugin/cmd/kube-scheduler/app/server.go:590: Failed to list *v1.Pod: Get https://10.25.123.11:6443/api/v1/pods?fieldSelector=spec.schedulerName%3Ddefault-scheduler%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded&limit=500&resourceVersion=0: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:51:34.818346       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolumeClaim: Get https://10.25.123.11:6443/api/v1/persistentvolumeclaims?limit=500&resourceVersion=0: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:51:34.818408       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.StatefulSet: Get https://10.25.123.11:6443/apis/apps/v1beta1/statefulsets?limit=500&resourceVersion=0: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:51:34.819028       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: Get https://10.25.123.11:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:51:34.819386       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Node: Get https://10.25.123.11:6443/api/v1/nodes?limit=500&resourceVersion=0: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:51:34.820217       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.ReplicaSet: Get https://10.25.123.11:6443/apis/extensions/v1beta1/replicasets?limit=500&resourceVersion=0: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:51:34.820659       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolume: Get https://10.25.123.11:6443/api/v1/persistentvolumes?limit=500&resourceVersion=0: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:51:34.821783       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.ReplicationController: Get https://10.25.123.11:6443/api/v1/replicationcontrollers?limit=500&resourceVersion=0: dial tcp 10.25.123.11:6443: getsockopt: connection refused
E0309 19:51:38.320455       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list poddisruptionbudgets.policy at the cluster scope
E0309 19:51:38.329101       1 reflector.go:205] k8s.io/kubernetes/plugin/cmd/kube-scheduler/app/server.go:590: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list pods at the cluster scope
E0309 19:51:38.329733       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list replicationcontrollers at the cluster scope
E0309 19:51:38.332670       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.ReplicaSet: replicasets.extensions is forbidden: User "system:kube-scheduler" cannot list replicasets.extensions at the cluster scope
E0309 19:51:38.332707       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list nodes at the cluster scope
E0309 19:51:38.332734       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list persistentvolumeclaims at the cluster scope
E0309 19:51:38.334248       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:kube-scheduler" cannot list persistentvolumes at the cluster scope
E0309 19:51:38.334568       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list statefulsets.apps at the cluster scope
E0309 19:51:38.334594       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: services is forbidden: User "system:kube-scheduler" cannot list services at the cluster scope
E0309 19:51:39.322884       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list poddisruptionbudgets.policy at the cluster scope
E0309 19:51:39.331726       1 reflector.go:205] k8s.io/kubernetes/plugin/cmd/kube-scheduler/app/server.go:590: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list pods at the cluster scope
E0309 19:51:39.333093       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list replicationcontrollers at the cluster scope
E0309 19:51:39.335939       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.ReplicaSet: replicasets.extensions is forbidden: User "system:kube-scheduler" cannot list replicasets.extensions at the cluster scope
E0309 19:51:39.335988       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list nodes at the cluster scope
E0309 19:51:39.336229       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list persistentvolumeclaims at the cluster scope
E0309 19:51:39.336514       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:kube-scheduler" cannot list persistentvolumes at the cluster scope
E0309 19:51:39.337881       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list statefulsets.apps at the cluster scope
E0309 19:51:39.338784       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: services is forbidden: User "system:kube-scheduler" cannot list services at the cluster scope
E0309 19:51:40.323869       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list poddisruptionbudgets.policy at the cluster scope
E0309 19:51:40.332910       1 reflector.go:205] k8s.io/kubernetes/plugin/cmd/kube-scheduler/app/server.go:590: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list pods at the cluster scope
E0309 19:51:40.334120       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list replicationcontrollers at the cluster scope
E0309 19:51:40.337188       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.ReplicaSet: replicasets.extensions is forbidden: User "system:kube-scheduler" cannot list replicasets.extensions at the cluster scope
E0309 19:51:40.338218       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list nodes at the cluster scope
E0309 19:51:40.339267       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list persistentvolumeclaims at the cluster scope
E0309 19:51:40.340635       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:kube-scheduler" cannot list persistentvolumes at the cluster scope
E0309 19:51:40.342035       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list statefulsets.apps at the cluster scope
E0309 19:51:40.343070       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: services is forbidden: User "system:kube-scheduler" cannot list services at the cluster scope
E0309 19:51:41.325987       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list poddisruptionbudgets.policy at the cluster scope
E0309 19:51:41.334782       1 reflector.go:205] k8s.io/kubernetes/plugin/cmd/kube-scheduler/app/server.go:590: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list pods at the cluster scope
E0309 19:51:41.336320       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list replicationcontrollers at the cluster scope
E0309 19:51:41.338996       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.ReplicaSet: replicasets.extensions is forbidden: User "system:kube-scheduler" cannot list replicasets.extensions at the cluster scope
E0309 19:51:41.339923       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list nodes at the cluster scope
E0309 19:51:41.340904       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list persistentvolumeclaims at the cluster scope
E0309 19:51:41.342304       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:kube-scheduler" cannot list persistentvolumes at the cluster scope
E0309 19:51:41.343675       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list statefulsets.apps at the cluster scope
E0309 19:51:41.344622       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: services is forbidden: User "system:kube-scheduler" cannot list services at the cluster scope
E0309 19:51:42.328038       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list poddisruptionbudgets.policy at the cluster scope
E0309 19:51:42.336744       1 reflector.go:205] k8s.io/kubernetes/plugin/cmd/kube-scheduler/app/server.go:590: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list pods at the cluster scope
E0309 19:51:42.338239       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list replicationcontrollers at the cluster scope
E0309 19:51:42.340719       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.ReplicaSet: replicasets.extensions is forbidden: User "system:kube-scheduler" cannot list replicasets.extensions at the cluster scope
E0309 19:51:42.341878       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list nodes at the cluster scope
E0309 19:51:42.342835       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list persistentvolumeclaims at the cluster scope
E0309 19:51:42.344100       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:kube-scheduler" cannot list persistentvolumes at the cluster scope
E0309 19:51:42.345231       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list statefulsets.apps at the cluster scope
E0309 19:51:42.346405       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: services is forbidden: User "system:kube-scheduler" cannot list services at the cluster scope
E0309 19:51:43.330230       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list poddisruptionbudgets.policy at the cluster scope
E0309 19:51:43.338706       1 reflector.go:205] k8s.io/kubernetes/plugin/cmd/kube-scheduler/app/server.go:590: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list pods at the cluster scope
E0309 19:51:43.339941       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list replicationcontrollers at the cluster scope
E0309 19:51:43.342476       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.ReplicaSet: replicasets.extensions is forbidden: User "system:kube-scheduler" cannot list replicasets.extensions at the cluster scope
E0309 19:51:43.343584       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list nodes at the cluster scope
E0309 19:51:43.344615       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list persistentvolumeclaims at the cluster scope
E0309 19:51:43.345792       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:kube-scheduler" cannot list persistentvolumes at the cluster scope
E0309 19:51:43.346976       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list statefulsets.apps at the cluster scope
E0309 19:51:43.348050       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: services is forbidden: User "system:kube-scheduler" cannot list services at the cluster scope
E0309 19:51:44.332307       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list poddisruptionbudgets.policy at the cluster scope
E0309 19:51:44.340659       1 reflector.go:205] k8s.io/kubernetes/plugin/cmd/kube-scheduler/app/server.go:590: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list pods at the cluster scope
E0309 19:51:44.341607       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list replicationcontrollers at the cluster scope
E0309 19:51:44.344223       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.ReplicaSet: replicasets.extensions is forbidden: User "system:kube-scheduler" cannot list replicasets.extensions at the cluster scope
E0309 19:51:44.345380       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list nodes at the cluster scope
E0309 19:51:44.346247       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list persistentvolumeclaims at the cluster scope
E0309 19:51:44.347536       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolume: persistentvolumes is forbidden: User "system:kube-scheduler" cannot list persistentvolumes at the cluster scope
E0309 19:51:44.348664       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list statefulsets.apps at the cluster scope
E0309 19:51:44.349648       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Service: services is forbidden: User "system:kube-scheduler" cannot list services at the cluster scope
E0309 19:51:45.334228       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:kube-scheduler" cannot list poddisruptionbudgets.policy at the cluster scope
E0309 19:51:45.342638       1 reflector.go:205] k8s.io/kubernetes/plugin/cmd/kube-scheduler/app/server.go:590: Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list pods at the cluster scope
E0309 19:51:45.343460       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.ReplicationController: replicationcontrollers is forbidden: User "system:kube-scheduler" cannot list replicationcontrollers at the cluster scope
E0309 19:51:45.345969       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1beta1.ReplicaSet: replicasets.extensions is forbidden: User "system:kube-scheduler" cannot list replicasets.extensions at the cluster scope
E0309 19:51:45.347140       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.Node: nodes is forbidden: User "system:kube-scheduler" cannot list nodes at the cluster scope
E0309 19:51:45.348176       1 reflector.go:205] k8s.io/kubernetes/vendor/k8s.io/client-go/informers/factory.go:86: Failed to list *v1.PersistentVolumeClaim: persistentvolumeclaims is forbidden: User "system:kube-scheduler" cannot list persistentvolumeclaims at the cluster scope

================================================== ======================

KELUARAN LOG UNTUK gcr.io/google_containers/pause-amd64:3.0

================================================== ======================

KELUARAN LOG UNTUK gcr.io/google_containers/pause-amd64:3.0

================================================== ======================

KELUARAN LOG UNTUK gcr.io/google_containers/pause-amd64:3.0

================================================== ======================

KELUARAN LOG UNTUK gcr.io/google_containers/pause-amd64:3.0

================================================== ======================

edwardofclt pada 9 Mar 2018

+1
Memperbarui:
Setelah melihat-lihat semua yang saya bisa (saya agak baru di k8s) akhirnya saya menemukan bahwa kubectl describe pod -n kube-system kube-dns-<sha> menunjukkan bahwa server virtual tempat saya menginstal hanya memiliki 1 CPU dan kube-dns tidak mulai jatuh tempo untuk kurang dalam CPU. Anehnya kubectl logs pod -n kube-system kube-dns-<sha> tidak menampilkan informasi ini.

Ini bekerja setelah menginstal ulang OS (sebagai reboot setelah instalasi kubeadm membuat master k8s gagal untuk memulai dengan benar).
(maaf lupa mengabadikan outputnya)

bbruun pada 12 Mar 2018

QQ-ing pada 14 Mar 2018

Saya memiliki masalah yang sama, membatalkan dan menjalankan reset dan kemudian init yang sama seperti sebelumnya tetapi dengan --apiserver-advertise-address=<my_host_public_ip_address> -- dan berhasil.

VaverDariush pada 15 Mar 2018

👍2

https://github.com/kubernetes/kubernetes/issues/59680#issuecomment -364646304
menonaktifkan selinux membantu saya.

avielb pada 19 Mar 2018

😕7 👍7 👎6 🎉2 ❤1

menurunkan versi ke 1.8.10 memperbaiki masalah bagi saya.

cbluth pada 24 Mar 2018

👍5

gabrielfsousa pada 27 Mar 2018

nevotheless pada 1 Apr 2018

Masalah yang sama di sini dengan v1.9.3 di Ubuntu 16.04 (tanpa selinux)

jpmondet pada 1 Apr 2018

+1 masalah yang sama

duongmngo pada 2 Apr 2018

Masalah yang sama dengan v1.10 di Ubuntu 16.04 di arm64.

farfeduc pada 4 Apr 2018

👍8

masalah yang sama dengan v1.10 di ubuntu 16.04 di arm64 (tanpa selinux)

therealqxing pada 5 Apr 2018

Periksa jumlah CPU yang Anda miliki di hadware yang Anda instal - 2 diperlukan pada master untuk menginstal seperti yang saya tulis di atas lebih dari 3 minggu yang lalu.

bbruun pada 5 Apr 2018

😕1 👍1

@bbruun Perangkat keras yang digunakan adalah: https://www.pine64.org/?page_id=1491 jadi 4 core dan terdeteksi dengan benar seperti itu. Perangkat keras seharusnya tidak menjadi masalah saat itu. Tapi terima kasih untuk tipnya. Mungkin @qxing3 tidak menggunakan perangkat keras yang sama...

farfeduc pada 5 Apr 2018

@farfeduc itu adalah penghalang jalan yang saya tekan, beberapa percobaan berturut-turut dengan menginstal ulang mesin virtual saya untuk menguji instalasi dan mengenal k8s, tetapi mengeluarkan log yang dapat digunakan dari sistem adalah hal yang membingungkan dan saya mencoba mendapatkannya dari mana pun saya bisa sampai saya mendapat pesan tentang tidak cukupnya cpu yang tersedia. Sekarang saya telah membeli 3 Udoo x86 Ultra untuk menjalankan cluster kecil untuk dimainkan di rumah bersama dengan pekerjaan di mana kami menggunakan instance yang sedikit lebih besar :-)

bbruun pada 5 Apr 2018

@bbruun Saya mengonfigurasi 2 cpu untuk mesin virtual saya, terima kasih atas tipnya.

therealqxing pada 5 Apr 2018

/assign @liztio

timothysc pada 7 Apr 2018

wu0407 pada 8 Apr 2018

+1 v1.10.0

manojakondi pada 13 Apr 2018

+1 v1.10.0 dan 1.10.1

TechnoRoss pada 13 Apr 2018

cleversonledur pada 13 Apr 2018

Yang cukup menarik, saya menemukan delta tergantung di mana saya menyebarkan. Saya berharap menemukan waktu untuk menjelajah lebih jauh, tetapi sejauh ini, saya tahu ini. Jika saya menggunakan Mac/VMware Fusion dan menjalankan CentOS 7 VM, saya dapat menggunakan kubeadm 1.8 dengan sukses penuh. Saya tidak pernah mendapatkan v1.9 atau v1.10 untuk bekerja secara lokal. Namun, menggunakan gambar CentOS 7 di Digital Ocean, saya dapat menjalankan v1.8.x, v1.10.0 dan v1.10.1 dengan sukses; v1.9 tampaknya "hanya bergantung" untuk beberapa alasan. Jadi sekarang, ini masalah menggali delta halus antara dua lingkungan untuk mencari tahu apa yang membuat sakelar itu berjalan. Saya tahu tingkat Kernel/patch cocok, serta mesin Docker, dll. LAKUKAN menginstal hal-hal cloud-init, VM lokal saya tidak, dan terus dan terus. Tidak sepele untuk mencari tahu apa yang berbeda. Saya melangkah lebih jauh dengan mencoba mencocokkan ukuran disk (berpikir disk yang lebih kecil mungkin menutupi beberapa kesalahan di suatu tempat, tetapi menghilangkannya juga).

Dalam semua kasus, menarik gambar selalu berhasil, itu hanya membuat layanan API merespons dan tidak terus mendaur ulang setiap beberapa menit ketika gagal.

TechnoRoss pada 14 Apr 2018

Salam pembuka,

Anda dapat merujuk ke https://docs.docker.com/config/daemon/systemd/#httphttps -proxy untuk mengatur proxy untuk daemon buruh pelabuhan.

guhuajun pada 16 Apr 2018

+1 Berjalan di HypriotOS di Raspberry PI 3

hansamann pada 18 Apr 2018

Saya dapat membuatnya bekerja dengan menginstal v1.9.6 alih-alih versi terakhir.
Jadi ini bekerja secara normal dengan v1.9.6 tetapi gagal dengan v1.10.0 dan v1.10.1 di ubuntu 16.04 di arm64 di papan sopine.

farfeduc pada 18 Apr 2018

👍1

Saya memiliki masalah yang sama pada Raspberry Pi 3, HypriotOS. Menurunkan versi ke 1.9.7-00 juga berhasil untuk saya.

JoeJasinski pada 22 Apr 2018

👍1

+1, kubeadm v1.10.1, raspberry pi 3b, hypriotOS

kocoten1992 pada 22 Apr 2018

Dalam kasus saya, saya menemukan bahwa wadah etcd memulai dan kemudian keluar dengan kesalahan, dan ini menyebabkan kubeadm init hang dan akhirnya waktu habis.

Untuk memeriksa apakah ini menggigit Anda, jalankan docker ps -a dan periksa status wadah etcd. Jika tidak berjalan, periksa log untuk wadah etcd ( docker logs <container-id> ), dan lihat apakah itu mengeluh karena tidak dapat mengikat ke alamat. Lihat laporan masalah ini: https://github.com/kubernetes/kubernetes/issues/57709

Masalah yang baru saja saya sebutkan memiliki solusi, tetapi pastikan itu yang Anda hadapi terlebih dahulu.

loudsong pada 27 Apr 2018

👍1

Pastikan firewall Anda mengizinkan lalu lintas masuk pada 6443

Misalnya, jika Anda menggunakan Ubuntu, jalankan ufw status untuk melihat apakah itu diaktifkan

Kemudian ufw allow 6443 untuk membuka port

aaronkjones pada 1 Mei 2018

apakah mungkin daftar gambar di bawah ini, dan kami menariknya secara manual dengan proxy, lalu init kubeadm lagi.
apakah itu akan berhasil?
cuz, kami berada di Cina, Anda tahu, GFW.
Dan saya baru mengenal k8s, terjebak di sini saat mengatur centos7.

HanYL-coder pada 17 Mei 2018

❤1

Untuk orang-orang di China yang berada di balik THE GREAT FIREWALL

thanch2n pada 17 Mei 2018

👍1

@thanch2n terima kasih banyak. Aku akan mencobanya.

HanYL-coder pada 18 Mei 2018

Saya menambahkan proxy ke buruh pelabuhan, menggunakan this , gambar tampaknya semua sudah diunduh, tetapi masih macet "[init] Ini mungkin perlu satu menit atau lebih lama jika gambar bidang kontrol harus ditarik.".

daftar gambar yang ditarik otomatis di bawah ini.

k8s.gcr.io/kube-apiserver-amd64 v1.10.2 e774f647e259 2 minggu lalu 225 MB
k8s.gcr.io/kube-scheduler-amd64 v1.10.2 0dcb3dea0db1 2 minggu yang lalu 50.4 MB
k8s.gcr.io/kube-controller-manager-amd64 v1.10.2 f3fcd0775c4e 2 minggu yang lalu 148 MB
k8s.gcr.io/etcd-amd64 3.1.12 52920ad46f5b 2 bulan lalu 193 MB
k8s.gcr.io/pause-amd64 3.1 da86e6ba6ca1 4 bulan lalu 742 kB

HanYL-coder pada 18 Mei 2018

Saya menghabiskan begitu banyak waktu mencoba untuk mencari tahu ini. Saya menonaktifkan ufw, mematikan selinux, memastikan penerusan ip aktif dan juga /proc/sys/net/bridge/bridge-nf-call-iptables disetel ke 1. Sepertinya tidak ada yang menyelesaikan masalah.

Akhirnya saya putuskan untuk downgrade lalu upgrade.

sudo apt-get -y --allow-downgrades install kubectl=1.5.3-00 kubelet=1.5.3-00 kubernetes-cni=0.3.0.1-07a8a2-00 dan

curl -Lo /tmp/old-kubeadm.deb https://apt.k8s.io/pool/kubeadm_1.6.0-alpha.0.2074-a092d8e0f95f52-00_amd64_0206dba536f698b5777c7d210444a8ace18f48e045ab78687327631c6c694f42.deb

untuk menurunkan versi dari 1,10 dan kemudian hanya

sudo apt-get -y install kubectl kubelet kubernetes-cni kubeadm

Dll sedang memulai ulang dan server api kehabisan waktu. Setelah beberapa saat, api-server restart dengan keluhan tidak dapat terhubung. Apakah ada cara agar pencatatan tingkat DEBUG diaktifkan? Sekarang yakin apa yang menyebabkan ini. Tapi itu bekerja sekarang. Saya pasti ingin mereproduksi ini dan memecahkan masalah.

mendoncangelo pada 19 Mei 2018

👍2

Aku punya alasan mengapa aku terjebak.
Saya menjalankannya di vmware dan menemukan 1G RAM, k8s membutuhkan setidaknya 2G RAM.
Apakah ada kemungkinan untuk menambahkan pemberitahuan tentang ini?

HanYL-coder pada 22 Mei 2018

+1 kubeadm 1.10.2 di CentOS 7
4GB RAM 2CPU

FNaughton pada 25 Mei 2018

+1 kubeadm 1.10.1 pada Debian Stretch (go1.9.3) pada HyperV VM dengan 6GB RAM dan 1 VCPU...

itu bekerja dengan baik di masa lalu karena saya membuat ulang cluster berkali-kali ...

simmessa pada 28 Mei 2018

Mencoba beralih ke 2 VCPU di HyperV, tidak ada perubahan.

simmessa pada 28 Mei 2018

+1!

imedaouidene pada 29 Mei 2018

+1. kubeadm 1.10.1, Peregangan Debian. Bekerja sebelumnya

egism pada 1 Jun 2018

Menemukan bahwa dengan buruh pelabuhan 1.13.1 pada Centos 7 kami melihat masalah dengan driver penyimpanan. Log Docker menunjukkan 'readlink /var/lib/docker/overlay2/l: argumen tidak valid'. Pindah ke docker 18.03.1-ce tampaknya menyelesaikan masalah ini dan kubeadm init tidak lagi hang.

FNaughton pada 1 Jun 2018

Saya memiliki masalah yang sama. Ternyata etcd menarik nama host mesin linux (somedomain.example.com), mencarinya di server DNS, menemukan jawaban untuk domain wildcard (*.example.com) dan mencoba mengikat ke alamat IP yang dikembalikan alih-alih apiserver-address-address.

Evengard pada 6 Jun 2018

Ada sejumlah perbaikan untuk pra-penarikan serta deteksi batas waktu pivot sehingga menutup masalah ini.

timothysc pada 12 Jun 2018

tejp1002 pada 30 Okt 2018

Mencoba cara standar membiarkan k8sadmin menarik gambar ke bawah, mencoba berkali-kali kemudian Menarik gambar, mengatur ulang, mencoba mengabaikan kesalahan, selalu gagal.

pi@master-node-001 :~ $ sudo kubeadm reset
[reset] PERINGATAN: perubahan yang dilakukan pada host ini oleh 'kubeadm init' atau 'kubeadm join' akan dikembalikan.
[preflight] menjalankan pemeriksaan pra-penerbangan
[reset] menghentikan layanan kubelet
[reset] melepas direktori mount di "/var/lib/kubelet"
[reset] menghapus isi direktori stateful: [/var/lib/kubelet /etc/cni/net.d /var/lib/dockershim /var/run/kubernetes /var/lib/etcd]
[reset] menghapus konten direktori konfigurasi: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] menghapus file: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler. conf]
pi@master-node-001 :~ $ kubeadm config gambar tarik
[config/images] Menarik k8s.gcr.io/kube- apiserver:v1.12.2
[config/images] Menarik k8s.gcr.io/kube-controller- manager:v1.12.2
[config/images] Menarik k8s.gcr.io/kube- scheduler:v1.12.2
[config/images] Menarik k8s.gcr.io/kube- proxy:v1.12.2
[config/images] Menarik k8s.gcr.io/ pause:3.1
[config/images] Menarik k8s.gcr.io/ etcd:3.2.24
[config/images] Menarik k8s.gcr.io/ coredns:1.2.2
pi@master-node-001 :~ $ sudo kubeadm init --token-ttl=0 --ignore-preflight-errors=all
[init] menggunakan versi Kubernetes: v1.12.2
[preflight] menjalankan pemeriksaan pra-penerbangan
[preflight/images] Diperlukan pengambilan gambar untuk menyiapkan cluster Kubernetes
[preflight/images] Ini mungkin memakan waktu satu atau dua menit, tergantung pada kecepatan koneksi internet Anda
[preflight/images] Anda juga dapat melakukan tindakan ini sebelumnya menggunakan 'kubeadm config images pull'
[kubelet] Menulis file lingkungan kubelet dengan flag ke file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet] Menulis konfigurasi kubelet ke file "/var/lib/kubelet/config.yaml"
[preflight] Mengaktifkan layanan kubelet
[sertifikat] Sertifikat dan kunci etcd/ca yang dihasilkan.
[sertifikat] Membuat sertifikat dan kunci apiserver-etcd-client.
[sertifikat] Membuat sertifikat dan kunci etcd/server.
[sertifikat] etcd/server servis cert ditandatangani untuk nama DNS [master-node-001 localhost] dan IP [127.0.0.1 ::1]
[sertifikat] Membuat sertifikat dan kunci etcd/peer.
[sertifikat] etcd/peer serve cert ditandatangani untuk nama DNS [master-node-001 localhost] dan IP [192.168.0.100 127.0.0.1 ::1]
[sertifikat] Membuat sertifikat dan kunci etcd/healthcheck-client.
[sertifikat] Sertifikat dan kunci ca yang dihasilkan.
[sertifikat] Sertifikat dan kunci apiserver yang dihasilkan.
[sertifikat] sertifikat penyajian apiserver ditandatangani untuk nama DNS [master-node-001 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] dan IP [10.96.0.1 192.168.0.100]
[sertifikat] Membuat sertifikat dan kunci apiserver-kubelet-client.
[sertifikat] Sertifikat dan kunci front-proxy-ca yang dihasilkan.
[sertifikat] Sertifikat dan kunci klien-proksi-depan yang dibuat.
[sertifikat] sertifikat dan kunci yang valid sekarang ada di "/etc/kubernetes/pki"
[sertifikat] Dihasilkan sa kunci dan kunci publik.
[kubeconfig] Tulis file KubeConfig ke disk: "/etc/kubernetes/admin.conf"
[kubeconfig] Tulis file KubeConfig ke disk: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Tulis file KubeConfig ke disk: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Tulis file KubeConfig ke disk: "/etc/kubernetes/scheduler.conf"
[controlplane] menulis manifes Static Pod untuk komponen kube-apiserver ke "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] menulis manifes Static Pod untuk komponen kube-controller-manager ke "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] menulis manifes Static Pod untuk komponen kube-scheduler ke "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Tulis manifes Pod Statis untuk instance etcd lokal ke "/etc/kubernetes/manifests/etcd.yaml"
[init] menunggu kubelet mem-boot control plane sebagai Static Pods dari direktori "/etc/kubernetes/manifests"
[init] ini mungkin memakan waktu satu menit atau lebih lama jika gambar bidang kontrol harus ditarik

Sayangnya, telah terjadi kesalahan:
time out menunggu kondisi

Kesalahan ini kemungkinan disebabkan oleh:
- Kubelet tidak berjalan
- Kubelet tidak sehat karena kesalahan konfigurasi node dalam beberapa cara (cgroup yang diperlukan dinonaktifkan)

Jika Anda menggunakan sistem yang didukung systemd, Anda dapat mencoba memecahkan masalah kesalahan dengan perintah berikut:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'

Selain itu, komponen bidang kontrol mungkin mengalami crash atau keluar saat dimulai oleh runtime container.
Untuk memecahkan masalah, buat daftar semua container menggunakan CLI runtime container pilihan Anda, misalnya buruh pelabuhan.
Berikut adalah salah satu contoh bagaimana Anda dapat membuat daftar semua kontainer Kubernetes yang berjalan di buruh pelabuhan:
- ' buruh pelabuhan ps -a | grep kube | grep -v jeda'
Setelah Anda menemukan wadah yang gagal, Anda dapat memeriksa lognya dengan:
- 'log buruh pelabuhan CONTAINERID'
tidak dapat menginisialisasi cluster Kubernetes
pi@master-node-001 :~ $ gambar buruh pelabuhan
UKURAN GAMBAR ID TAG REPOSITORY DIBUAT
k8s.gcr.io/kube-controller-manager v1.12.2 4bc6cae738d8 7 hari yang lalu 146MB
k8s.gcr.io/kube-apiserver v1.12.2 8bfe044a05e1 7 hari yang lalu 177MB
k8s.gcr.io/kube-scheduler v1.12.2 3abf5566fec1 7 hari yang lalu 52MB
k8s.gcr.io/kube-proxy v1.12.2 328ef67ca54f 7 hari yang lalu 84.5MB
k8s.gcr.io/kube-proxy v1.12.1 8c06fbe56458 3 minggu yang lalu 84.7MB
k8s.gcr.io/kube-controller-manager v1.12.1 5de943380295 3 minggu yang lalu 146MB
k8s.gcr.io/kube-scheduler v1.12.1 1fbc2e4cd378 3 minggu yang lalu 52MB
k8s.gcr.io/kube-apiserver v1.12.1 ab216fe6acf6 3 minggu lalu 177MB
k8s.gcr.io/etcd 3.2.24 e7a8884c8443 5 minggu lalu 222MB
k8s.gcr.io/coredns 1.2.2 ab0805b0de94 2 bulan lalu 33.4MB
k8s.gcr.io/kube-scheduler v1.11.0 0e4a34a3b0e6 4 bulan yang lalu 56.8MB
k8s.gcr.io/kube-controller-manager v1.11.0 55b70b420785 4 bulan yang lalu 155MB
k8s.gcr.io/etcd 3.2.18 b8df3b177be2 6 bulan lalu 219MB
k8s.gcr.io/pause 3.1 e11a8cbeda86 10 bulan lalu 374kB
pi@master-node-001 :~ $ j | grep kubectl
-bash: h: perintah tidak ditemukan
pi@master-node-001 :~ $ sejarah | grep kubectl
9 daftar pod kubectl
10 pod daftar kubectl
11 kubectl --help
12 kubectl dapatkan pod -o lebar
14 kubectl dapatkan pod -o lebar
32 jam | grep kubectl
33 sejarah | grep kubectl
pi@master-node-001 :~ $ !12
kubectl dapatkan pod -o lebar
Tidak dapat terhubung ke server: net/http: TLS handshake timeout
pi@master-node-001 :~ $ sejarah | grep jeda
17 buruh pelabuhan ps -a | grep kube | grep -v jeda
35 sejarah | grep jeda
pi@master-node-001 :~ $ !17
buruh pelabuhan ps -a | grep kube | grep -v jeda
41623613679e 8bfe044a05e1 "kube-apiserver --au..." 29 detik yang lalu Naik 14 detik k8s_kube-apiserver_kube-apiserver-master-node-001_kube-system_1ec53f8ef96c76af95c78c809252f05c_3
0870760b9ea0 8bfe044a05e1 "kube-apiserver --au..." 2 menit yang lalu Keluar (0) 33 detik yang lalu k8s_kube-apiserver_kube-apiserver-master-node-001_kube-system_1ec53f8ef96c76af95c78c809252f05c_2
c60d65fab8a7 3abf5566fec1 "kube-scheduler --ad..." 6 menit yang lalu Naik 5 menit k8s_kube-scheduler_kube-scheduler-master-node-001_kube-system_ee7b1077c61516320f4273309e9b4690_0
26c58f6c68e9 e7a8884c8443 "etcd --advertise-cl..." 6 menit yang lalu Naik 5 menit k8s_etcd_etcd-master-node-001_kube-system_d01dcc7fc79b875a52f01e26432e6745_0
65546081ca77 4bc6cae738d8 "kube-controller-man…" 6 menit yang lalu Naik 5 menit k8s_kube-controller-manager_kube-controller-manager-master-node-001_kube-system_07e19bc9fea1626927c12244604bdb2f_0
pi@master-node-001 :~ $ kubectl dapatkan pod -o lebar
^C
pi@master-node-001 :~ $ sudo reboot
Koneksi ke 192.168.0.100 ditutup oleh host jarak jauh.
Koneksi ke 192.168.0.100 ditutup.
karl@karl-PL62-7RC :~$ ping 192.168.0.100
PING 192.168.0.100 (192.168.0.100) 56(84) byte data.
^C
--- 192.168.0.100 statistik ping ---
2 paket terkirim, 0 diterima, 100% paket hilang, waktu 1015ms

karl@karl-PL62-7RC :~$ ssh [email protected]
ssh_exchange_identification: baca: Koneksi disetel ulang oleh rekan
karl@karl-PL62-7RC :~$ ssh [email protected]
[email protected] kata sandi:
Linux master-node-001 4.14.71-v7+ #1145 SMP Jum 21 Sep 15:38:35 BST 2018 armv7l

Program yang disertakan dengan sistem Debian GNU/Linux adalah perangkat lunak bebas;
istilah distribusi yang tepat untuk setiap program dijelaskan dalam
file individu di /usr/share/doc/*/copyright.

Debian GNU/Linux hadir dengan BENAR-BENAR TANPA GARANSI, sejauh
diperbolehkan oleh hukum yang berlaku.
Login terakhir: Rabu 31 Okt 21:36:13 2018
pi@master-node-001 :~ $ kubectl dapatkan pod -o lebar
Sambungan ke server 192.168.0.100:6443 ditolak - apakah Anda menentukan host atau port yang benar?
pi@master-node-001 :~ $ sudo kubeadm init --token-ttl=0 --ignore-preflight-errors=all
[init] menggunakan versi Kubernetes: v1.12.2
[preflight] menjalankan pemeriksaan pra-penerbangan
[PERINGATAN FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml sudah ada
[PERINGATAN FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml sudah ada
[PERINGATAN FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml sudah ada
[PERINGATAN FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml sudah ada
[PERINGATAN Port-10250]: Port 10250 sedang digunakan
[PERINGATAN DirAvailable--var-lib-etcd]: /var/lib/etcd tidak kosong
[preflight/images] Diperlukan pengambilan gambar untuk menyiapkan cluster Kubernetes
[preflight/images] Ini mungkin memakan waktu satu atau dua menit, tergantung pada kecepatan koneksi internet Anda
[preflight/images] Anda juga dapat melakukan tindakan ini sebelumnya menggunakan 'kubeadm config images pull'
[kubelet] Menulis file lingkungan kubelet dengan flag ke file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet] Menulis konfigurasi kubelet ke file "/var/lib/kubelet/config.yaml"
[preflight] Mengaktifkan layanan kubelet
[sertifikat] Menggunakan sertifikat dan kunci etcd/peer yang ada.
[sertifikat] Menggunakan sertifikat dan kunci apiserver-etcd-client yang ada.
[sertifikat] Menggunakan sertifikat dan kunci etcd/server yang ada.
[sertifikat] Menggunakan sertifikat dan kunci klien etcd/healthcheck yang ada.
[sertifikat] Menggunakan sertifikat dan kunci apiserver yang ada.
[sertifikat] Menggunakan sertifikat dan kunci apiserver-kubelet-client yang ada.
[sertifikat] Menggunakan sertifikat dan kunci klien-proksi-depan yang ada.
[sertifikat] sertifikat dan kunci yang valid sekarang ada di "/etc/kubernetes/pki"
[sertifikat] Menggunakan kunci sa yang ada.
[kubeconfig] Menggunakan file KubeConfig terbaru yang ada: "/etc/kubernetes/admin.conf"
[kubeconfig] Menggunakan file KubeConfig terbaru yang ada: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Menggunakan file KubeConfig terbaru yang ada: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Menggunakan file KubeConfig terbaru yang ada: "/etc/kubernetes/scheduler.conf"
[controlplane] menulis manifes Static Pod untuk komponen kube-apiserver ke "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] menulis manifes Static Pod untuk komponen kube-controller-manager ke "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] menulis manifes Static Pod untuk komponen kube-scheduler ke "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Tulis manifes Pod Statis untuk instance etcd lokal ke "/etc/kubernetes/manifests/etcd.yaml"
[init] menunggu kubelet mem-boot control plane sebagai Static Pods dari direktori "/etc/kubernetes/manifests"
[init] ini mungkin memakan waktu satu menit atau lebih lama jika gambar bidang kontrol harus ditarik

Sayangnya, telah terjadi kesalahan:
time out menunggu kondisi

Kesalahan ini kemungkinan disebabkan oleh:
- Kubelet tidak berjalan
- Kubelet tidak sehat karena kesalahan konfigurasi node dalam beberapa cara (cgroup yang diperlukan dinonaktifkan)

Jika Anda menggunakan sistem yang didukung systemd, Anda dapat mencoba memecahkan masalah kesalahan dengan perintah berikut:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'

fenwk0 pada 31 Okt 2018

13 sudo kubeadm init --token-ttl=0
14 kubectl dapatkan pod -o lebar
15 sudo kubeadm reset
16 sudo kubeadm init --token-ttl=0
17 buruh pelabuhan ps -a | grep kube | grep -v jeda
18 gambar konfigurasi kubeadm tarik --kubernetes-version=v1.11.0
19 sudo kubeadm reset
20 sejarah > catatan.txt
21 catatan lagi.txt
22 sudo reboot
23 daftar gambar konfigurasi kubeadm
24 gambar konfigurasi kubeadm tarik --kubernetes-version=v1.11.0
25 sudo kubeadm init --token-ttl=0 --ignore-preflight-errors=all
26 gambar konfigurasi kubeadm menarik
27 sudo kubeadm init --token-ttl=0 --ignore-preflight-errors=all
28 gambar konfigurasi kubeadm tarik
29 sudo kubeadm reset
30 gambar konfigurasi kubeadm menarik
31 sudo kubeadm init --token-ttl=0 --ignore-preflight-errors=all
32 gambar buruh pelabuhan
33 jam | grep kubectl
34 sejarah | grep kubectl
35 kubectl dapatkan pod -o lebar
36 sejarah | grep jeda
37 buruh pelabuhan ps -a | grep kube | grep -v jeda
38 kubectl dapatkan pod -o lebar
39 sudo reboot
40 kubectl dapatkan pod -o lebar
41 sudo kubeadm init --token-ttl=0 --ignore-preflight-errors=all