From 4f7826376827b8b629b051bf1c6ac265f33df585 Mon Sep 17 00:00:00 2001 From: Carlos Esteban Lopez Jaramillo Date: Tue, 30 Aug 2022 17:12:28 -0500 Subject: [PATCH] docs: Update docs/features/kubernetes/authentication.md Co-authored-by: Jamie Klassen Signed-off-by: Carlos Esteban Lopez Jaramillo --- docs/features/kubernetes/authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/kubernetes/authentication.md b/docs/features/kubernetes/authentication.md index 3bb3733109..71d0d7b758 100644 --- a/docs/features/kubernetes/authentication.md +++ b/docs/features/kubernetes/authentication.md @@ -25,7 +25,7 @@ The providers available as server side are: These providers authenticate your _user_ with the cluster. Each Backstage user will be prompted for credentials and will have access to the clusters as long as the user has been authorized -to access said cluster, if the cluster is listed in the `clusterLocatorMethods` in the +to access said cluster. If the cluster is listed in the `clusterLocatorMethods` in the config, but the user hasn't been authorized to access, the user will see the cluster listed but will not see any resources in the plugin page for that cluster, and the error will show as `401` or similar.