whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

bootstrap-tokens: promote to GA in 1.18 (#18428)

Browse Source
This commit is contained in:
Lubomir I. Ivanov
2020-01-17 07:18:56 +02:00
committed by Kubernetes Prow Robot
parent 1ae1305680
commit 946bce1b33
3 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/access-authn-authz/authentication.md
+1 -1
View File
@@ -120,7 +120,7 @@ Authorization: Bearer 31ada4fd-adec-460c-809a-9e56ceb75269
### Bootstrap Tokens ### Bootstrap Tokens
This feature is currently in **beta**. {{< feature-state for_k8s_version="v1.18" state="stable" >}}
To allow for streamlined bootstrapping for new clusters, Kubernetes includes a To allow for streamlined bootstrapping for new clusters, Kubernetes includes a
dynamically-managed Bearer token type called a *Bootstrap Token*. These tokens dynamically-managed Bearer token type called a *Bootstrap Token*. These tokens
content/en/docs/reference/access-authn-authz/bootstrap-tokens.md
+4 -3
View File
@@ -7,6 +7,9 @@ weight: 20
--- ---
{{% capture overview %}} {{% capture overview %}}
{{< feature-state for_k8s_version="v1.18" state="stable" >}}
Bootstrap tokens are a simple bearer token that is meant to be used when Bootstrap tokens are a simple bearer token that is meant to be used when
creating new clusters or joining new nodes to an existing cluster. It was built creating new clusters or joining new nodes to an existing cluster. It was built
to support [kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/), but can be used in other contexts to support [kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/), but can be used in other contexts
@@ -26,8 +29,6 @@ Controller Manager. The tokens are also used to create a signature for a
specific ConfigMap used in a "discovery" process through a BootstrapSigner specific ConfigMap used in a "discovery" process through a BootstrapSigner
controller. controller.
{{< feature-state state="beta" >}}
## Token Format ## Token Format
Bootstrap Tokens take the form of `abcdef.0123456789abcdef`. More formally, Bootstrap Tokens take the form of `abcdef.0123456789abcdef`. More formally,
@@ -115,7 +116,7 @@ authenticate to the API server as a bearer token.
`cluster-info` ConfigMap as described below. `cluster-info` ConfigMap as described below.
The `expiration` field controls the expiry of the token. Expired tokens are The `expiration` field controls the expiry of the token. Expired tokens are
rejected when used for authentication and ignored during ConfigMap signing. rejected when used for authentication and ignored during ConfigMap signing.
The expiry value is encoded as an absolute UTC time using RFC3339. Enable the The expiry value is encoded as an absolute UTC time using RFC3339. Enable the
`tokencleaner` controller to automatically delete expired tokens. `tokencleaner` controller to automatically delete expired tokens.
content/en/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping.md
+1 -1
View File
@@ -117,7 +117,7 @@ While any authentication strategy can be used for the kubelet's initial
bootstrap credentials, the following two authenticators are recommended for ease bootstrap credentials, the following two authenticators are recommended for ease
of provisioning. of provisioning.
1. [Bootstrap Tokens](#bootstrap-tokens) - __beta__ 1. [Bootstrap Tokens](#bootstrap-tokens)
2. [Token authentication file](#token-authentication-file) 2. [Token authentication file](#token-authentication-file)
Bootstrap tokens are a simpler and more easily managed method to authenticate kubelets, and do not require any additional flags when starting kube-apiserver. Bootstrap tokens are a simpler and more easily managed method to authenticate kubelets, and do not require any additional flags when starting kube-apiserver.