Failed to start kubelet and kube-proxy if TLS is disabled

[Debo Zhang]

Use fedora-atomic-20180419, disable TLS, and then deploy a kubernetes cluster. Kubelet and kube-proxy started failed.

For kube-proxy, error message is as follows:
invalid configuration: [unable to read client-cert /etc/kubernetes/certs/proxy.crt for kube-proxy due to open /etc/kubernetes/certs/proxy.crt: no such file or directory, unable to read client-key /etc/kubernetes/certs/proxy.key for kube-proxy due to open /etc/kubernetes/certs/proxy.key: no such file or directory, unable to read certificate-authority /etc/kubernetes/certs/ca.crt for kubernetes due to open /etc/kubernetes/certs/ca.crt: no such file or directory]

For kubelet, error message is as follows:
unable to load client CA file /etc/kubernetes/certs/ca.crt: open /etc/kubernetes/certs/ca.crt: no such file or directory

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Debo Zhang (laun-zhangdebo)]

I have fixed this bug, please review:
https://review.openstack.org/#/c/602283/