added doc for setting up cloud provider kubectl auth via plugin

Signed-off-by: GitHub <noreply@github.com>
pull/44134/head
Suruchi Kumari 2023-11-29 13:26:04 +00:00 committed by GitHub
parent efe2fc9319
commit c0a72d25d8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 16 additions and 1 deletions

View File

@ -888,6 +888,10 @@ protocol specific logic, then returns opaque credentials to use. Almost all cred
use cases require a server side component with support for the [webhook token authenticator](#webhook-token-authentication)
to interpret the credential format produced by the client plugin.
{{< note >}}
Earlier versions of `kubectl` included built-in support for authenticating to AKS and GKE, but this is no longer present.
{{< /note >}}
### Example use case
In a hypothetical use case, an organization would run an external service that exchanges LDAP credentials

View File

@ -35,4 +35,15 @@ If kubectl cluster-info returns the url response but you can't access your clust
```shell
kubectl cluster-info dump
```
```
{{< note >}}
### Troubleshooting the 'No Auth Provider Found' Error Message
In Kubernetes **v1.26**, kubectl removed the built-in authentication for the following cloud
providers managed Kubernetes offerings. These providers have released kubectl plugins to provide the cloud-specific authentication. For instructions, refer to the following provider documentation:
* AKS (Azure): [kubelogin plugin](https://github.com/Azure/kubelogin)
* GKE (Google Cloud): [gke-gcloud-auth-plugin](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#install_plugin)
{{< /note >}}