Clayton Coleman caf2e70aa1 When bootstrapping a client cert, store it with other client certs ...

The kubelet uses two different locations to store certificates on
initial bootstrap and then on subsequent rotation:

* bootstrap: certDir/kubelet-client.(crt|key)
* rotation:  certDir/kubelet-client-(DATE|current).pem

Bootstrap also creates an initial node.kubeconfig that points to the
certs. Unfortunately, with short rotation the node.kubeconfig then
becomes out of date because it points to the initial cert/key, not the
rotated cert key.

Alter the bootstrap code to store client certs exactly as if they would
be rotated (using the same cert Store code), and reference the PEM file
containing cert/key from node.kubeconfig, which is supported by kubectl
and other Go tooling. This ensures that the node.kubeconfig continues to
be valid past the first expiration.

Kubernetes-commit: 368959346af6e06085c63a4cc7c37839f262f636

2018-04-04 21:56:15 -04:00

..

csr

sync: initially remove files BUILD */BUILD BUILD.bazel */BUILD.bazel

2018-03-15 09:19:38 +00:00

certificate_manager_test.go

fix some syntax related errors

2018-02-11 19:50:49 +08:00

certificate_manager.go

When using the bootstrap cert, update the store

2018-02-04 01:24:56 -05:00

certificate_store_test.go

Move certificate manager to client.

2017-03-09 16:34:55 -08:00

certificate_store.go

When bootstrapping a client cert, store it with other client certs

2018-04-04 21:56:15 -04:00

OWNERS

Move certificate manager to client.

2017-03-09 16:34:55 -08:00