paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 21 Packages Projects Releases Wiki Activity

docs: Address MR comments

Browse Source 
Signed-off-by: Carlos Esteban Lopez <lcarlosesteb@vmware.com>
This commit is contained in:
Carlos Esteban Lopez
2022-09-12 13:00:26 -05:00
committed by Carlos Lopez
parent d12ebdde77
commit cc05706f35
1 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/kubernetes/authentication.md
+10 -4
View File
@@ -18,7 +18,9 @@ The providers currently available are divided into server side and client side.
## Server Side Providers
These providers authenticate your _application_ with the cluster, meaning anyone that is
logged in into your backstage app will be granted the same access to Kubernetes objects.
logged in into your backstage app will be granted the same access to Kubernetes objects,
to put an example,even guest users would have access to the cluster resources, so be
careful of using server side providers with guest access enabled.
The providers available as server side are:
@@ -31,9 +33,13 @@ The providers available as server side are:
### Azure
The Azure server side authentication provider works by authenticating on the server with
the Azure CLI `az login`, meaning any user that can access the backstage app will have
the same level of access to the cluster in the Kubernetes plugin, to put an example, even
guest users would have access to the cluster resources.
the Azure CLI, follow these steps:
- Install the Azure CLI: https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest
- Login with your Azure/Microsoft account with `az login` in the server's terminal
- Go to your AKS cluster's resource page in Azure Console and follow the steps in the
`Connect` tab to set the subscription and get your credentials for `kubectl` integration
- Configure your cluster to use the `azure` auth provider like this:
```yaml
kubernetes: