Kubernetes HA领导者控制平面服务重启

当遵循kubernetes-the-hard-way并将其移植到本地Ubuntu 16.04 VM时，启动HA控制平面给我带来了问题。当选领导者的kube-apiserver和kube-controller-manager服务保持失败并重新启动，但其他两位非领导者主控制器上的控制面显示正常。此行为遵循集群周围的领导者。Kubernetes HA领导者控制平面服务重启

ETCD看上去很幸福：

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-API服务器日志： Pastebin apiserver logs

KUBE-控制器 -

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

我已经通过验证了当前领导经理日志： Pastebin controller logs

来源

2017-09-13 MrShushhh

考虑到日志中的各种“存储”相关错误，并且由于这与领导者选举有关，所以我认为或许这个问题可能与etcd有关。 Etcd不断报告。对于笑脸，我从api-server.service中删除--experimental-encryption-provider-config=/var/lib/kubernetes/encryption-config.yaml \\，现在控制面板很开心。

我不确定是否加密本身是破坏事物，或者如果我的加密自动化处理它。

来源

2017-09-15 14:19:46 MrShushhh

Kubernetes HA领导者控制平面服务重启

回答

相关问题