You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To enable API bearer tokens (including service account tokens) to be used to authenticate to the kubelet's HTTPS endpoint:
70
69
-->
71
-
要启用 API 持有者令牌(包括服务帐户令牌)以对 kubelet 的 HTTPS 端点进行身份验证,请执行以下操作:
70
+
要启用 API 持有者令牌(包括服务账号令牌)以对 kubelet 的 HTTPS 端点进行身份认证,请执行以下操作:
72
71
73
72
<!--
74
73
* ensure the `authentication.k8s.io/v1beta1` API group is enabled in the API server
@@ -82,12 +81,12 @@ To enable API bearer tokens (including service account tokens) to be used to aut
82
81
<!--
83
82
## Kubelet authorization
84
83
-->
85
-
## Kubelet 鉴权 {#kubelet-authorization}
84
+
## kubelet 鉴权 {#kubelet-authorization}
86
85
87
86
<!--
88
87
Any request that is successfully authenticated (including an anonymous request) is then authorized. The default authorization mode is `AlwaysAllow`, which allows all requests.
89
88
-->
90
-
任何成功通过身份验证的请求(包括匿名请求)之后都会被鉴权。
89
+
任何成功通过身份认证的请求(包括匿名请求)之后都会被鉴权。
91
90
默认的鉴权模式为 `AlwaysAllow`,它允许所有请求。
92
91
93
92
<!--
@@ -100,9 +99,9 @@ There are many possible reasons to subdivide access to the kubelet API:
100
99
* bearer token auth is enabled, but arbitrary API users' (like service accounts) ability to call the kubelet API should be limited
101
100
* client certificate auth is enabled, but only some of the client certificates signed by the configured CA should be allowed to use the kubelet API
102
101
-->
103
-
*启用了匿名身份验证,但是应限制匿名用户调用 kubelet API 的能力
104
-
* 启用了持有者令牌认证,但应限制任意 API 用户(如服务帐户)调用 kubelet API 的能力
105
-
*启用了客户端证书身份验证,但仅应允许已配置的 CA 签名的某些客户端证书使用 kubelet API
102
+
*启用了匿名身份认证,但是应限制匿名用户调用 kubelet API 的能力
103
+
* 启用了持有者令牌认证,但应限制任意 API 用户(如服务账号)调用 kubelet API 的能力
104
+
*启用了客户端证书身份认证,但仅应允许已配置的 CA 签名的某些客户端证书使用 kubelet API
106
105
107
106
<!--
108
107
To subdivide access to the kubelet API, delegate authorization to the API server:
@@ -122,9 +121,9 @@ To subdivide access to the kubelet API, delegate authorization to the API server
122
121
<!--
123
122
The kubelet authorizes API requests using the same [request attributes](/docs/reference/access-authn-authz/authorization/#review-your-request-attributes) approach as the apiserver.
0 commit comments