Merge pull request #44134 from coder12git/sur/2

Document setting up cloud provider kubectl auth via plugin (AKS, GKE)

Author: k8s-ci-robot

content/en/docs/reference/access-authn-authz/authentication.md

@@ -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

content/en/docs/tasks/tools/included/verify-kubectl.md

@@ -35,4 +35,14 @@ If kubectl cluster-info returns the url response but you can't access your clust
 
 ```shell
 kubectl cluster-info dump
-```
+```
+
+### Troubleshooting the 'No Auth Provider Found' error message {#no-auth-provider-found}
+
+In Kubernetes 1.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:
+
+* Azure  AKS: [kubelogin plugin](https://azure.github.io/kubelogin/)
+* Google Kubernetes Engine: [gke-gcloud-auth-plugin](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#install_plugin)
+
+(There could also be other reasons to see the same error message, unrelated to that change.)