kubelet uses self-signed serving certs

[mfojtik]

After #420 merged, we are not setting the ca field for kubeletClientInfo which will cause the kube-apiserver->kubelet communication is insecure because the kubelet identity is not checked.

/assign @sjenning

[ashcrow]

Is this still an issue? We seem to be seeing the following now:

Nov 30 20:19:34 test1-master-0 hyperkube[2875]: I1130 20:19:34.843859    2875 logs.go:49] http: TLS handshake error from 192.168.126.51:49656: remote error: tls: bad certificate
Nov 30 20:19:45 test1-master-0 hyperkube[2875]: I1130 20:19:45.660350    2875 logs.go:49] http: TLS handshake error from 192.168.126.51:49698: remote error: tls: bad certificate

Ref: openshift/machine-config-operator#199

[sjenning]

this is the last bit openshift/machine-config-operator#187

[crawford]

/close

[openshift-ci-robot]

@crawford: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.