Wrong URL for kubelet-tls-bootstrapping
The URL is https://kubernetes.io/docs/admin/kubelet-tls-bootstrapping/
This commit is contained in:
parent
2b96cb3fd0
commit
d41c5973f2
|
@ -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
|
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
|
for users that wish to start clusters without `kubeadm`. It is also built to
|
||||||
work, via RBAC policy, with the [Kubelet TLS
|
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 Tokens are defined with a specific type
|
||||||
(`bootstrap.kubernetes.io/token`) of secrets that lives in the `kube-system`
|
(`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
|
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.
|
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
|
`07401b.f395accd246ae52d`) as the shared secret. Users _must_ verify that HS256
|
||||||
is used.
|
is used.
|
||||||
|
|
Loading…
Reference in New Issue