在遵循kubernetes-the-hard-way并将其移植到本地Ubuntu 16.04 VM时，启动HA控制平面给我带来了问题。为选举产生的领导者提供的kube-apiserver和kube-controller-manager服务不断失败并重新启动，但另外两位非领导者的控制平面也很好。此行为遵循群集周围的领导者。
EtcD看起来很开心：
Rectangle rect = new Rectangle(164, 190, 164, 110);
chunk_text.setAnnotation(PdfAnnotation.createText(writer, rect, "Warning", comments, false, "Comment"));
PdfContentByte pdb = new PdfContentByte(writer);
chunk_free.setAnnotation(PdfAnnotation.createFreeText(writer, rect, comments, pdb));
chunk_popup.setAnnotation(PdfAnnotation.createPopup(writer, rect, comments, false));
我通过以下方式验证了当前的领导者：
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
kube-apiserver日志：
Pastebin apiserver logs
kube-controller-manager日志：
Pastebin controller logs
答案 0 :(得分：0)
考虑各种＆＃34;存储＆＃34;日志中的相关错误，因为这与领导者选举有关，我想也许这个问题可能与etd有关。 Etcd保持报告不错。对于grins，我从api-server.service中删除了--experimental-encryption-provider-config=/var/lib/kubernetes/encryption-config.yaml \\，现在控制窗格很高兴。
我不确定加密本身是否破坏了事情，或者我的加密自动化是否会加剧它。