From a27d7d3bd58ec64c852d14ee2bde8aaea1a18d0b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9s=20Mauricio=20G=C3=B3mez=20P?= Date: Wed, 21 Feb 2024 17:29:29 -0500 Subject: [PATCH] Update docs/features/kubernetes/authstrategies.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Jamie Klassen Signed-off-by: Andrés Mauricio Gómez P --- docs/features/kubernetes/authstrategies.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/features/kubernetes/authstrategies.md b/docs/features/kubernetes/authstrategies.md index 6b8ee45fc4..e6e43ab1cf 100644 --- a/docs/features/kubernetes/authstrategies.md +++ b/docs/features/kubernetes/authstrategies.md @@ -20,9 +20,9 @@ kubernetes clusters, it includes: - `Client Side Providers` like `aks` or `oidc` where the user is authenticated with the cluster, getting only the kubernetes permissions granted to that specific user. -Although there are `Server Side Providers` and `Client Side Providers`, an auth provider requires to have code on both sides, perhaps one of them doing -most of the authentication job, but notice that not all steps to authenticate against a Kubernetes Cluster are always executed exclusively on the server side or client side. -A Kubernetes authentication flow could require to split the authentication process among steps on the client side **and** steps on the server side. +Although there are `Server Side Providers` and `Client Side Providers`, authenticating with a cluster requires code on both sides. Perhaps one of them does +most of the job, but in general not all steps to authenticate against a Kubernetes cluster are always executed exclusively on the server side or client side. +A Kubernetes authentication flow could require splitting the authentication process among steps on the client side **and** steps on the server side. ## AuthenticationStrategy interface