Incorporated suggestions for provideClusterInfo paragraph
Signed-off-by: Margo Crawford <margaretc@vmware.com>
This commit is contained in:
parent
5accf8f128
commit
67a750b5e0
|
@ -1004,13 +1004,12 @@ RFC3339 timestamp. Presence or absence of an expiry has the following impact:
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
To provide the plugin with information about the cluster for which it is
|
To enable the exec plugin to obtain cluster-specific information, set `provideClusterInfo` on the `user.exec`
|
||||||
obtaining credentials, the `provideClusterInfo` field can be set on the exec user
|
|
||||||
field in the [kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/).
|
field in the [kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/).
|
||||||
The plugin will then be supplied with an environment variable, `KUBERNETES_EXEC_INFO`.
|
The plugin will then be supplied with an environment variable, `KUBERNETES_EXEC_INFO`.
|
||||||
Information from this environment variable can be used to perform cluster-specific
|
Information from this environment variable can be used to perform cluster-specific
|
||||||
credential acquisition logic. Here is an example of the aforementioned
|
credential acquisition logic.
|
||||||
`KUBERNETES_EXEC_INFO` environment variable.
|
The following `ExecCredential` manifest describes a cluster information sample.
|
||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
|
|
Loading…
Reference in New Issue