From c2c2835ef5af723766d9881a1aa4cd87d2a551aa Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Tue, 30 Jul 2024 14:15:09 -0700 Subject: [PATCH] Apply 89d94841 (added Azure AD to the provider list of the kubectl utility) to /v2.8 and /v2.9 --- .../reference-guides/cli-with-rancher/kubectl-utility.md | 1 + .../reference-guides/cli-with-rancher/kubectl-utility.md | 1 + 2 files changed, 2 insertions(+) diff --git a/versioned_docs/version-2.8/reference-guides/cli-with-rancher/kubectl-utility.md b/versioned_docs/version-2.8/reference-guides/cli-with-rancher/kubectl-utility.md index b3f49191ede..5b863d2e4be 100644 --- a/versioned_docs/version-2.8/reference-guides/cli-with-rancher/kubectl-utility.md +++ b/versioned_docs/version-2.8/reference-guides/cli-with-rancher/kubectl-utility.md @@ -32,5 +32,6 @@ This feature enables kubectl to authenticate with the Rancher server and get a n 3. FreeIPA 4. OpenLDAP 5. SAML providers: Ping, Okta, ADFS, Keycloak, Shibboleth +6. Azure AD When you first run kubectl, for example, `kubectl get pods`, you are prompted to pick an auth provider and log in with the Rancher server. The kubeconfig token is cached in the path where you run kubectl under `./.cache/token`. This token is valid until [it expires](../../api/api-tokens.md#disable-tokens-in-generated-kubeconfigs), or [gets deleted from the Rancher server](../../api/api-tokens.md#deleting-tokens). Upon expiration, you must log in with the Rancher server again to run the `kubectl get pods` command. diff --git a/versioned_docs/version-2.9/reference-guides/cli-with-rancher/kubectl-utility.md b/versioned_docs/version-2.9/reference-guides/cli-with-rancher/kubectl-utility.md index b3f49191ede..5b863d2e4be 100644 --- a/versioned_docs/version-2.9/reference-guides/cli-with-rancher/kubectl-utility.md +++ b/versioned_docs/version-2.9/reference-guides/cli-with-rancher/kubectl-utility.md @@ -32,5 +32,6 @@ This feature enables kubectl to authenticate with the Rancher server and get a n 3. FreeIPA 4. OpenLDAP 5. SAML providers: Ping, Okta, ADFS, Keycloak, Shibboleth +6. Azure AD When you first run kubectl, for example, `kubectl get pods`, you are prompted to pick an auth provider and log in with the Rancher server. The kubeconfig token is cached in the path where you run kubectl under `./.cache/token`. This token is valid until [it expires](../../api/api-tokens.md#disable-tokens-in-generated-kubeconfigs), or [gets deleted from the Rancher server](../../api/api-tokens.md#deleting-tokens). Upon expiration, you must log in with the Rancher server again to run the `kubectl get pods` command.