Skip to content

Commit d148026

Browse files
authored
Merge pull request #26065 from margocrawf/master
Rewording of paragraph about provideClusterInfo key on Authentication page
2 parents 6e95a6b + 67a750b commit d148026

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

content/en/docs/reference/access-authn-authz/authentication.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1004,14 +1004,12 @@ RFC3339 timestamp. Presence or absence of an expiry has the following impact:
10041004
}
10051005
}
10061006
```
1007-
1008-
The plugin can optionally be called with an environment variable, `KUBERNETES_EXEC_INFO`,
1009-
that contains information about the cluster for which this plugin is obtaining
1010-
credentials. This information can be used to perform cluster-specific credential
1011-
acquisition logic. In order to enable this behavior, the `provideClusterInfo` field must
1012-
be set on the exec user field in the
1013-
[kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/). Here is an
1014-
example of the aforementioned `KUBERNETES_EXEC_INFO` environment variable.
1007+
To enable the exec plugin to obtain cluster-specific information, set `provideClusterInfo` on the `user.exec`
1008+
field in the [kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/).
1009+
The plugin will then be supplied with an environment variable, `KUBERNETES_EXEC_INFO`.
1010+
Information from this environment variable can be used to perform cluster-specific
1011+
credential acquisition logic.
1012+
The following `ExecCredential` manifest describes a cluster information sample.
10151013

10161014
```json
10171015
{

0 commit comments

Comments
 (0)