Merge pull request #26065 from margocrawf/master
Rewording of paragraph about provideClusterInfo key on Authentication page
This commit is contained in:
@@ -1004,14 +1004,12 @@ RFC3339 timestamp. Presence or absence of an expiry has the following impact:
|
|||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
To enable the exec plugin to obtain cluster-specific information, set `provideClusterInfo` on the `user.exec`
|
||||||
The plugin can optionally be called with an environment variable, `KUBERNETES_EXEC_INFO`,
|
field in the [kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/).
|
||||||
that contains information about the cluster for which this plugin is obtaining
|
The plugin will then be supplied with an environment variable, `KUBERNETES_EXEC_INFO`.
|
||||||
credentials. This information can be used to perform cluster-specific credential
|
Information from this environment variable can be used to perform cluster-specific
|
||||||
acquisition logic. In order to enable this behavior, the `provideClusterInfo` field must
|
credential acquisition logic.
|
||||||
be set on the exec user field in the
|
The following `ExecCredential` manifest describes a cluster information sample.
|
||||||
[kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/). Here is an
|
|
||||||
example of the aforementioned `KUBERNETES_EXEC_INFO` environment variable.
|
|
||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
|
|||||||
Reference in New Issue
Block a user