From d41c5973f28f07f3238e9adb1d76b608bb44d46d Mon Sep 17 00:00:00 2001 From: Bruno Vernay Date: Wed, 29 Mar 2017 14:16:50 +0200 Subject: [PATCH] Wrong URL for kubelet-tls-bootstrapping The URL is https://kubernetes.io/docs/admin/kubelet-tls-bootstrapping/ --- docs/admin/bootstrap-tokens.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/admin/bootstrap-tokens.md b/docs/admin/bootstrap-tokens.md index 0bbe59d095..5140e68c1b 100644 --- a/docs/admin/bootstrap-tokens.md +++ b/docs/admin/bootstrap-tokens.md @@ -14,7 +14,7 @@ creating new clusters or joining new nodes to an existing cluster. It was built to support [`kubeadm`](/docs/admin/kubeadm/), but can be used in other contexts for users that wish to start clusters without `kubeadm`. It is also built to work, via RBAC policy, with the [Kubelet TLS -Bootstrap](/docs/admin/kubelet-tls-bootstrap/) system. +Bootstrapping](/docs/admin/kubelet-tls-bootstrapping/) system. Bootstrap Tokens are defined with a specific type (`bootstrap.kubernetes.io/token`) of secrets that lives in the `kube-system` @@ -168,4 +168,4 @@ rules (base64 encoded while discarding any trailing `=`). That encoded payload is then used to form a whole JWS by inserting it between the 2 dots. You can verify the JWS using the `HS256` scheme (HMAC-SHA256) with the full token (e.g. `07401b.f395accd246ae52d`) as the shared secret. Users _must_ verify that HS256 -is used. \ No newline at end of file +is used.