Kubernetes HA leader控制平面服务重新启动

Question

在遵循kubernetes- the -hard-way并将其移植到本地Ubuntu 16.04VM时，启动HA控制平面给我带来了问题。为当选的领导者提供的kube-apiserver和kube-controller-manager服务不断出现故障并重新启动，但其他两个非领导者主机上的控制平面运行良好。这种行为跟随leader在集群周围运行。

EtcD看起来很高兴：

member 7f44a7567a5e995 is healthy: got healthy result from https://10.1.15.117:2379
member 43d2258c438cbf4e is healthy: got healthy result from https://10.1.15.116:2379
member a83b22e9f907f471 is healthy: got healthy result from https://10.1.15.115:2379
cluster is healthy

我已经通过以下方式确认了当前的领导者：

kubectl get endpoints kube-controller-manager --namespace=kube-system  -o yaml


apiVersion: v1
kind: Endpoints
metadata:
  annotations:
    control-plane.alpha.kubernetes.io/leader: '{"holderIdentity":"df-dev-kube-test02","leaseDurationSeconds":15,"acquireTime":"2017-09-13T17:15:06Z","renewTime":"2017-09-13T18:10:46Z","leaderTransitions":7}'
  creationTimestamp: 2017-09-13T14:59:57Z
  name: kube-controller-manager
  namespace: kube-system
  resourceVersion: "7814"
  selfLink: /api/v1/namespaces/kube-system/endpoints/kube-controller-manager
  uid: 3599a959-9894-11e7-a34f-005056b24128
subsets: []

kube-apiserver日志：Pastebin apiserver logs

kube控制器管理器日志：Pastebin controller logs

Answer 1

考虑到日志中各种与“存储”相关的错误，而且由于这与领导人选举有关，我认为这个问题可能与etcd有关。不过，Etcd的报告一直很好。对于grins，我从api-server.service中删除了--experimental-encryption-provider-config=/var/lib/kubernetes/encryption-config.yaml \\，现在控制面板是满意的。

我不确定是加密本身破坏了一些东西，还是我的自动加密冲刷了它。