- 查看kube-apiserver状态
[root@yxz-cluster01 ~]# systemctl status kube-apiserver -l
● kube-apiserver.service - Kubernetes API Server
Loaded: loaded (/etc/systemd/system/kube-apiserver.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2019-05-09 20:38:59 CST; 5 days ago
Docs: https://github.com/GoogleCloudPlatform/kubernetes
Main PID: 14956 (kube-apiserver)
Tasks: 19
Memory: 341.0M
CGroup: /system.slice/kube-apiserver.service
└─14956 /usr/bin/kube-apiserver --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,ResourceQuota,NodeRestriction,MutatingAdmissionWebhook,ValidatingAdmissionWebhook --bind-address=192.168.50.10 --insecure-bind-address=127.0.0.1 --authorization-mode=Node,RBAC --kubelet-https=true --kubelet-client-certificate=/etc/kubernetes/ssl/admin.pem --kubelet-client-key=/etc/kubernetes/ssl/admin-key.pem --anonymous-auth=false --basic-auth-file=/etc/kubernetes/ssl/basic-auth.csv --service-cluster-ip-range=10.68.0.0/16 --service-node-port-range=20000-40000 --tls-cert-file=/etc/kubernetes/ssl/kubernetes.pem --tls-private-key-file=/etc/kubernetes/ssl/kubernetes-key.pem --client-ca-file=/etc/kubernetes/ssl/ca.pem --service-account-key-file=/etc/kubernetes/ssl/ca-key.pem --etcd-cafile=/etc/kubernetes/ssl/ca.pem --etcd-certfile=/etc/kubernetes/ssl/kubernetes.pem --etcd-keyfile=/etc/kubernetes/ssl/kubernetes-key.pem --etcd-servers=https://192.168.50.10:2379,https://192.168.50.11:2379,https://192.168.50.12:2379 --enable-swagger-ui=true --endpoint-reconciler-type=lease --allow-privileged=true --audit-log-maxage=30 --audit-log-maxbackup=3 --audit-log-maxsize=100 --audit-log-path=/var/lib/audit.log --event-ttl=1h --requestheader-client-ca-file=/etc/kubernetes/ssl/ca.pem --requestheader-allowed-names= --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --proxy-client-cert-file=/etc/kubernetes/ssl/aggregator-proxy.pem --proxy-client-key-file=/etc/kubernetes/ssl/aggregator-proxy-key.pem --enable-aggregator-routing=true --runtime-config=batch/v2alpha1=true --v=2
May 15 07:42:24 yxz-cluster01 kube-apiserver[14956]: E0515 07:42:24.078550 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
May 15 07:50:52 yxz-cluster01 kube-apiserver[14956]: E0515 07:50:52.107620 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
May 15 07:59:42 yxz-cluster01 kube-apiserver[14956]: E0515 07:59:42.206113 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
May 15 08:09:28 yxz-cluster01 kube-apiserver[14956]: E0515 08:09:28.309181 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
May 15 08:25:15 yxz-cluster01 kube-apiserver[14956]: E0515 08:25:15.320151 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
May 15 08:41:51 yxz-cluster01 kube-apiserver[14956]: E0515 08:41:51.362720 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
May 15 08:54:27 yxz-cluster01 kube-apiserver[14956]: E0515 08:54:27.414907 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
May 15 09:08:50 yxz-cluster01 kube-apiserver[14956]: E0515 09:08:50.468322 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
May 15 09:15:00 yxz-cluster01 kube-apiserver[14956]: E0515 09:15:00.530719 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
May 15 09:30:02 yxz-cluster01 kube-apiserver[14956]: E0515 09:30:02.619469 14956 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
问题原因: 这个是etcd的版本问题导致，不影响功能的使用