Comment 0 for bug 1792663

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:
failed to run Kubelet: invalid kubeconfig: Error loading config file "/etc/kubernetes/kubelet-config.yaml": yaml: line 17: mapping values are not allowed in this context

I checked kubelet-config.yaml, content is as follows:
apiVersion: v1
clusters:
- cluster:
    server: http://10.0.0.4:8080
  name: kubernetes
contexts:
- context:
    cluster: kubernetes
    user: system:node:gg-dejmst3uc4ji-minion-0
  name: default
current-context: default
kind: Config
preferences: {}
users:
- name: system:node:gg-dejmst3uc4ji-minion-0
    as-user-extra: {}

Watch the last three lines of kubelet-config.yaml, it's not correct.