Skip to content

Commit ed79e82

Browse files
authored
Merge pull request #32631 from my-git9/projected-volumes
[zh] Update projected-volumes.md
2 parents 14cbd8b + 74449d1 commit ed79e82

File tree

1 file changed

+11
-6
lines changed

1 file changed

+11
-6
lines changed

content/zh/docs/concepts/storage/projected-volumes.md

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Currently, the following types of volume sources can be projected:
3434
* [`secret`](/docs/concepts/storage/volumes/#secret)
3535
* [`downwardAPI`](/docs/concepts/storage/volumes/#downwardapi)
3636
* [`configMap`](/docs/concepts/storage/volumes/#configmap)
37-
* `serviceAccountToken`
37+
* [`serviceAccountToken`](#serviceaccounttoken)
3838
-->
3939
## 介绍 {#introduction}
4040

@@ -45,7 +45,7 @@ Currently, the following types of volume sources can be projected:
4545
* [`secret`](/zh/docs/concepts/storage/volumes/#secret)
4646
* [`downwardAPI`](/zh/docs/concepts/storage/volumes/#downwardapi)
4747
* [`configMap`](/zh/docs/concepts/storage/volumes/#configmap)
48-
* `serviceAccountToken`
48+
* [`serviceAccountToken`](#serviceaccounttoken)
4949

5050
<!--
5151
All sources are required to be in the same namespace as the Pod. For more details,
@@ -85,10 +85,12 @@ parameters are nearly the same with two exceptions:
8585
你可以显式地为每个投射单独设置 `mode` 属性。
8686

8787
<!--
88+
## serviceAccountToken projected volumes {#serviceaccounttoken}
8889
When the `TokenRequestProjection` feature is enabled, you can inject the token
8990
for the current [service account](/docs/reference/access-authn-authz/authentication/#service-account-tokens)
9091
into a Pod at a specified path. For example:
9192
-->
93+
## serviceAccountToken 投射卷 {#serviceaccounttoken}
9294
`TokenRequestProjection` 特性被启用时,你可以将当前
9395
[服务账号](/zh/docs/reference/access-authn-authz/authentication/#service-account-tokens)
9496
的令牌注入到 Pod 中特定路径下。例如:
@@ -97,14 +99,17 @@ into a Pod at a specified path. For example:
9799

98100
<!--
99101
The example Pod has a projected volume containing the injected service account
100-
token. This token can be used by a Pod's containers to access the Kubernetes API
101-
server. The `audience` field contains the intended audience of the
102+
token. Containers in this Pod can use that token to access the Kubernetes API
103+
server, authenticating with the identity of [the pod's ServiceAccount](/docs/tasks/configure-pod-container/configure-service-account/).
104+
The `audience` field contains the intended audience of the
102105
token. A recipient of the token must identify itself with an identifier specified
103106
in the audience of the token, and otherwise should reject the token. This field
104107
is optional and it defaults to the identifier of the API server.
105108
-->
106-
示例 Pod 中包含一个投射卷,其中包含注入的服务账号令牌。该令牌可以被 Pod
107-
中的容器用来访问 Kubernetes API 服务器。`audience` 字段包含令牌所针对的受众。
109+
示例 Pod 中包含一个投射卷,其中包含注入的服务账号令牌。
110+
此 Pod 中的容器可以使用该令牌访问 Kubernetes API 服务器, 使用
111+
[pod 的 ServiceAccount](/zh/docs/tasks/configure-pod-container/configure-service-account/)
112+
进行身份验证。`audience` 字段包含令牌所针对的受众。
108113
收到令牌的主体必须使用令牌受众中所指定的某个标识符来标识自身,否则应该拒绝该令牌。
109114
此字段是可选的,默认值为 API 服务器的标识。
110115

0 commit comments

Comments
 (0)