| 2016-08-08 22:41:12 |
hongbin |
description |
This is caused by https://review.openstack.org/#/c/345969/2/magnum/drivers/k8s_coreos_v1/templates/fragments/enable-kube-proxy-minion-coreos.yaml . The change above made the format incorrectly and removed the necessary path to locate the TLS secrets. |
This is caused by https://review.openstack.org/#/c/345969/2/magnum/drivers/k8s_coreos_v1/templates/fragments/enable-kube-proxy-minion-coreos.yaml . The change above made the format incorrectly and removed the necessary path to locate the TLS secrets.
The error:
Error: invalid configuration: [unable to read client-cert /etc/kubernetes/ssl/worker.pem for kubelet due to open /etc/kubernetes/ssl/worker.pem: no such file or directory, unable to read client-key /etc/kubernetes/ssl/worker-key.pem for kubelet due to open /etc/kubernetes/ssl/worker-key.pem: no such file or directory, unable to read certificate-authority /etc/kubernetes/ssl/ca.pem for local due to open /etc/kubernetes/ssl/ca.pem: no such file or directory]
invalid configuration: [unable to read client-cert /etc/kubernetes/ssl/worker.pem for kubelet due to open /etc/kubernetes/ssl/worker.pem: no such file or directory, unable to read client-key /etc/kubernetes/ssl/worker-key.pem for kubelet due to open /etc/kubernetes/ssl/worker-key.pem: no such file or directory, unable to read certificate-authority /etc/kubernetes/ssl/ca.pem for local due to open /etc/kubernetes/ssl/ca.pem: no such file or directory] |
|
