From 4b64338f153a776a085002d6103b6466524f0500 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Tue, 8 Oct 2019 04:23:11 +0100 Subject: [PATCH] Fix typo (#16728) --- .../docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md index 67128885c5..74f947b39e 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md @@ -106,13 +106,13 @@ These are advanced topics for users who need to integrate their organization's c ### Set up a signer The Kubernetes Certificate Authority does not work out of the box. -You can configure an external signer such as [cert-manager][cert-manager-issuer], or you can use the build-in signer. +You can configure an external signer such as [cert-manager][cert-manager-issuer], or you can use the built-in signer. The built-in signer is part of [`kube-controller-manager`][kcm]. -To activate the build-in signer, you pass the `--cluster-signing-cert-file` and `--cluster-signing-key-file` arguments. +To activate the built-in signer, you pass the `--cluster-signing-cert-file` and `--cluster-signing-key-file` arguments. The built-in signer is part of [`kube-controller-manager`][kcm]. -To activate the build-in signer, you must pass the `--cluster-signing-cert-file` and `--cluster-signing-key-file` flags. +To activate the built-in signer, you must pass the `--cluster-signing-cert-file` and `--cluster-signing-key-file` flags. If you're creating a new cluster, you can use a kubeadm [configuration file][config]: