From 44f8466d090db1fc161c6f8f7c7f9a7bdc496436 Mon Sep 17 00:00:00 2001 From: Mike Danese Date: Thu, 6 Apr 2017 14:06:08 -0700 Subject: [PATCH] tls: tell cluster admins how to enable the local signer --- docs/tasks/tls/managing-tls-in-a-cluster.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/tasks/tls/managing-tls-in-a-cluster.md b/docs/tasks/tls/managing-tls-in-a-cluster.md index 3c0e71cfea..57e3462ea6 100644 --- a/docs/tasks/tls/managing-tls-in-a-cluster.md +++ b/docs/tasks/tls/managing-tls-in-a-cluster.md @@ -195,3 +195,11 @@ noted in the previous section and the reprecussions of issuing a specific certificate should be fully understood before granting this permission. See [here](/docs/admin/authentication#x509-client-certs) for information on how certificates interact with authentication. + +## A Note to Cluster Administrators + +This tutorial assumes that a signer is setup to serve the certificates API. The +Kubernetes controller manager provides a default implementation of a signer. To +enable it, pass the `--cluster-signing-cert-file` and +`--cluster-signing-key-file` parameters to the controller manager with paths to +your Certificate Authority's keypair.