Skip to content

Commit 95aedc6

Browse files
my-git9my-git9
committed
[zh-cn]sync client-authentication.v1beta1
Signed-off-by: xin.li <[email protected]>
1 parent b8ea998 commit 95aedc6

1 file changed

Lines changed: 77 additions & 25 deletions

File tree

‎content/zh-cn/docs/reference/config-api/client-authentication.v1beta1.md‎

Lines changed: 77 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,10 @@ ExecCredential 由基于 exec 的插件使用，与 HTTP 传输组件沟通凭
3737
<a href="#client-authentication-k8s-io-v1beta1-ExecCredentialSpec"><code>ExecCredentialSpec</code></a>
3838
</td>
3939
<td>
40-
<!--Spec holds information passed to the plugin by the transport.-->
40+
<!--
41+
Spec holds information passed to the plugin by the transport.
42+
-->
43+
4144
字段 spec 包含由 HTTP 传输组件传递给插件的信息。
4245
</td>
4346
</tr>
@@ -47,8 +50,11 @@ ExecCredential 由基于 exec 的插件使用，与 HTTP 传输组件沟通凭
4750
<a href="#client-authentication-k8s-io-v1beta1-ExecCredentialStatus"><code>ExecCredentialStatus</code></a>
4851
</td>
4952
<td>
50-
<!--Status is filled in by the plugin and holds the credentials that the transport
51-
should use to contact the API.-->
53+
<!--
54+
Status is filled in by the plugin and holds the credentials that the transport
55+
should use to contact the API.
56+
-->
57+
5258
字段 status 由插件填充，包含传输组件与 API 服务器连接时需要提供的凭据。
5359
</td>
5460
</tr>
@@ -58,7 +64,9 @@ ExecCredential 由基于 exec 的插件使用，与 HTTP 传输组件沟通凭
5864

5965
## `Cluster` {#client-authentication-k8s-io-v1beta1-Cluster}
6066

61-
<!--**Appears in:**-->
67+
<!--
68+
**Appears in:**
69+
-->
6270
**出现在：**
6371

6472
- [ExecCredentialSpec](#client-authentication-k8s-io-v1beta1-ExecCredentialSpec)
@@ -72,8 +80,8 @@ with a kubernetes cluster (just like they would via a kubeconfig), the fields
7280
should shadow "k8s.io/client-go/tools/clientcmd/api/v1".Cluster, with the exception
7381
of CertificateAuthority, since CA data will always be passed to the plugin as bytes.
7482
-->
75-
Cluster 中包含允许 exec 插件与 Kubernetes 集群进行通信身份认证时所需
76-
的信息。
83+
Cluster 中包含允许 exec 插件与 Kubernetes
84+
集群进行通信身份认证时所需的信息。
7785

7886
为了确保该结构体包含需要与 Kubernetes 集群进行通信的所有内容（就像通过 Kubeconfig 一样），
7987
该字段应该映射到 "k8s.io/client-go/tools/clientcmd/api/v1".cluster，
@@ -88,7 +96,10 @@ Cluster 中包含允许 exec 插件与 Kubernetes 集群进行通信身份认证
8896
<code>string</code>
8997
</td>
9098
<td>
91-
<!--Server is the address of the kubernetes cluster (https://hostname:port).-->
99+
<!--
100+
Server is the address of the kubernetes cluster (https://hostname:port).
101+
-->
102+
92103
字段 server 是 Kubernetes 集群的地址（https://hostname:port）。
93104
</td>
94105
</tr>
@@ -141,7 +152,10 @@ If empty, system roots should be used.
141152
<code>string</code>
142153
</td>
143154
<td>
144-
<!--ProxyURL is the URL to the proxy to be used for all requests to this cluster.-->
155+
<!--
156+
ProxyURL is the URL to the proxy to be used for all requests to this cluster.
157+
-->
158+
145159
此字段用来设置向集群发送所有请求时要使用的代理服务器。
146160
</td>
147161
</tr>
@@ -151,14 +165,18 @@ If empty, system roots should be used.
151165
<code>bool</code>
152166
</td>
153167
<td>
168+
<p>
154169
<!--
155170
DisableCompression allows client to opt-out of response compression for all requests to the server. This is useful
156171
to speed up requests (specifically lists) when client-server network bandwidth is ample, by saving time on
157172
compression (server-side) and decompression (client-side): https://github.com/kubernetes/kubernetes/issues/112296.
158173
-->
159-
<p>disable-compression 允许客户端针对到服务器的所有请求选择取消响应压缩。
160-
当客户端服务器网络带宽充足时，这有助于通过节省压缩（服务器端）和解压缩（客户端）时间来加快请求（特别是列表）的速度：
161-
https://github.com/kubernetes/kubernetes/issues/112296。</p>
174+
175+
disable-compression 允许客户端针对到服务器的所有请求选择取消响应压缩。
176+
当客户端服务器网络带宽充足时，这有助于通过节省压缩（服务器端）和解压缩
177+
（客户端）时间来加快请求（特别是列表）的速度：
178+
https://github.com/kubernetes/kubernetes/issues/112296。
179+
</p>
162180
</td>
163181
</tr>
164182

@@ -167,17 +185,32 @@ If empty, system roots should be used.
167185
<a href="https://godoc.org/k8s.io/apimachinery/pkg/runtime/#RawExtension"><code>k8s.io/apimachinery/pkg/runtime.RawExtension</code></a>
168186
</td>
169187
<td>
188+
<p>
170189
<!--
171190
Config holds additional config data that is specific to the exec
172191
plugin with regards to the cluster being authenticated to.
173-
192+
-->
193+
此字段包含一些额外的、特定于 exec 插件和所连接的集群的数据。
194+
</p>
195+
<p>
196+
<!--
174197
This data is sourced from the clientcmd Cluster object's
175198
extensions[client.authentication.k8s.io/exec] field:
176199
-->
177-
<p>此字段包含一些额外的、特定于 exec 插件和所连接的集群的数据，</p>
178-
<p>此字段来自于 clientcmd 集群对象的 <code>extensions[client.authentication.k8s.io/exec]</code>
179-
字段：</p>
200+
此字段来自于 clientcmd 集群对象的
201+
<code>extensions[client.authentication.k8s.io/exec]</code> 字段：
202+
</p>
180203
<pre>
204+
<!--
205+
clusters:
206+
- name: my-cluster
207+
cluster:
208+
...
209+
extensions:
210+
- name: client.authentication.k8s.io/exec # reserved extension name for per cluster exec config
211+
extension:
212+
audience: 06e3fbd18de8 # arbitrary config
213+
-->
181214
clusters:
182215
- name: my-cluster
183216
cluster:
@@ -187,6 +220,7 @@ clusters:
187220
extension:
188221
audience: 06e3fbd18de8 # 任意配置信息
189222
</pre>
223+
<p>
190224
<!--
191225
In some environments, the user config may be exactly the same across many clusters
192226
(i.e. call this exec plugin) minus some details that are specific to each cluster
@@ -195,11 +229,12 @@ specified with the cluster info. Using this field to store secret data is not
195229
recommended as one of the prime benefits of exec plugins is that no secrets need
196230
to be stored directly in the kubeconfig.
197231
-->
198-
<p>在某些环境中，用户配置可能对很多集群而言都完全一样（即调用同一个 exec 插件），
232+
在某些环境中，用户配置可能对很多集群而言都完全一样（即调用同一个 exec 插件），
199233
只是针对不同集群会有一些细节上的差异，例如 audience。
200234
此字段使得特定于集群的配置可以直接使用集群信息来设置。
201235
不建议使用此字段来保存 Secret 数据，因为 exec 插件的主要优势之一是不需要在
202-
kubeconfig 中保存 Secret 数据。</p>
236+
Kubeconfig 中保存 Secret 数据。
237+
</p>
203238
</td>
204239
</tr>
205240

@@ -208,7 +243,9 @@ kubeconfig 中保存 Secret 数据。</p>
208243

209244
## `ExecCredentialSpec` {#client-authentication-k8s-io-v1beta1-ExecCredentialSpec}
210245

211-
<!-- **Appears in:** -->
246+
<!--
247+
**Appears in:**
248+
-->
212249
**出现在：**
213250

214251
- [ExecCredential](#client-authentication-k8s-io-v1beta1-ExecCredential)
@@ -235,7 +272,7 @@ ExecConfig.ProvideClusterInfo).
235272
-->
236273
此字段中包含的信息使得 exec 插件能够与要访问的 Kubernetes 集群通信。
237274
注意，cluster 字段只有在 exec 驱动的配置中 provideClusterInfo
238-
（即：ExecConfig.ProvideClusterInfo）被设置为 true 时才不能为空。
275+
（即：<code>ExecConfig.ProvideClusterInfo</code>）被设置为 true 时才不能为空。
239276
</td>
240277
</tr>
241278

@@ -244,7 +281,9 @@ ExecConfig.ProvideClusterInfo).
244281

245282
## `ExecCredentialStatus` {#client-authentication-k8s-io-v1beta1-ExecCredentialStatus}
246283

247-
<!-- **Appears in:** -->
284+
<!--
285+
**Appears in:**
286+
-->
248287
**出现在：**
249288

250289
- [ExecCredential](#client-authentication-k8s-io-v1beta1-ExecCredential)
@@ -269,13 +308,17 @@ exec 插件本身至少应通过文件访问许可来实施保护。
269308

270309
<table class="table">
271310
<thead><tr><th width="30%"><!--Field-->字段</th><th><!--Description-->描述</th></tr></thead>
311+
<tbody>
272312

273313
<tr>
274314
<td><code>expirationTimestamp</code><br/>
275-
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.32/#time-v1-meta"><code>meta/v1.Time</code></a>
315+
<a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.33/#time-v1-meta"><code>meta/v1.Time</code></a>
276316
</td>
277317
<td>
278-
<!-- ExpirationTimestamp indicates a time when the provided credentials expire. -->
318+
<!--
319+
ExpirationTimestamp indicates a time when the provided credentials expire.
320+
-->
321+
279322
给出所提供的凭据到期的时间。
280323
</td>
281324
</tr>
@@ -285,7 +328,10 @@ exec 插件本身至少应通过文件访问许可来实施保护。
285328
<code>string</code>
286329
</td>
287330
<td>
288-
<!-- Token is a bearer token used by the client for request authentication. -->
331+
<!--
332+
Token is a bearer token used by the client for request authentication.
333+
-->
334+
289335
客户端用做请求身份认证的持有者令牌。
290336
</td>
291337
</tr>
@@ -295,7 +341,10 @@ exec 插件本身至少应通过文件访问许可来实施保护。
295341
<code>string</code>
296342
</td>
297343
<td>
298-
<!-- PEM-encoded client TLS certificates (including intermediates, if any). -->
344+
<!--
345+
PEM-encoded client TLS certificates (including intermediates, if any).
346+
-->
347+
299348
PEM 编码的客户端 TLS 证书（如果有临时证书，也会包含）。
300349
</td>
301350
</tr>
@@ -305,7 +354,10 @@ exec 插件本身至少应通过文件访问许可来实施保护。
305354
<code>string</code>
306355
</td>
307356
<td>
308-
<!-- PEM-encoded private key for the above certificate. -->
357+
<!--
358+
PEM-encoded private key for the above certificate.
359+
-->
360+
309361
与上述证书对应的、PEM 编码的私钥。
310362
</td>
311363
</tr>

0 commit comments

Comments
 (0)