From 5accf8f1283ed0d76ef7e154597993b1afe68cd2 Mon Sep 17 00:00:00 2001 From: Margo Crawford Date: Fri, 8 Jan 2021 16:38:51 -0800 Subject: [PATCH 1/2] Rewording of paragraph about provideClusterInfo key Signed-off-by: Margo Crawford --- .../access-authn-authz/authentication.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/content/en/docs/reference/access-authn-authz/authentication.md b/content/en/docs/reference/access-authn-authz/authentication.md index c385a15fda..f88d8e2370 100644 --- a/content/en/docs/reference/access-authn-authz/authentication.md +++ b/content/en/docs/reference/access-authn-authz/authentication.md @@ -1004,14 +1004,13 @@ RFC3339 timestamp. Presence or absence of an expiry has the following impact: } } ``` - -The plugin can optionally be called with an environment variable, `KUBERNETES_EXEC_INFO`, -that contains information about the cluster for which this plugin is obtaining -credentials. This information can be used to perform cluster-specific credential -acquisition logic. In order to enable this behavior, the `provideClusterInfo` field must -be set on the exec user field in the -[kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/). Here is an -example of the aforementioned `KUBERNETES_EXEC_INFO` environment variable. +To provide the plugin with information about the cluster for which it is +obtaining credentials, the `provideClusterInfo` field can be set on the exec user +field in the [kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/). +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 +credential acquisition logic. Here is an example of the aforementioned +`KUBERNETES_EXEC_INFO` environment variable. ```json { From 67a750b5e01fabfeb2c2fb6447471a312a5a2605 Mon Sep 17 00:00:00 2001 From: Margo Crawford Date: Mon, 1 Feb 2021 15:35:49 -0800 Subject: [PATCH 2/2] Incorporated suggestions for provideClusterInfo paragraph Signed-off-by: Margo Crawford --- .../en/docs/reference/access-authn-authz/authentication.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/content/en/docs/reference/access-authn-authz/authentication.md b/content/en/docs/reference/access-authn-authz/authentication.md index f88d8e2370..d7a67f53ef 100644 --- a/content/en/docs/reference/access-authn-authz/authentication.md +++ b/content/en/docs/reference/access-authn-authz/authentication.md @@ -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 -obtaining credentials, the `provideClusterInfo` field can be set on the exec user +To enable the exec plugin to obtain cluster-specific information, set `provideClusterInfo` on the `user.exec` field in the [kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/). 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 -credential acquisition logic. Here is an example of the aforementioned -`KUBERNETES_EXEC_INFO` environment variable. +credential acquisition logic. +The following `ExecCredential` manifest describes a cluster information sample. ```json {