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

Update configuration.md

Browse Source 
The wording for the default behaviour reads a little odd.
I think this clears it up

Signed-off-by: David Martin <david-martin@users.noreply.github.com>
This commit is contained in:
David Martin
2023-12-15 12:08:58 +00:00
committed by GitHub
parent 79bff053f1
commit 9c20b935bc
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/kubernetes/configuration.md
+1 -1
View File
@@ -593,7 +593,7 @@ SingleTenant Cluster:
In the example above, we configured the "backstage.io/kubernetes-cluster" annotation on the entity `catalog-info.yaml` file to specify that the current component is running in a single cluster called "dice-cluster", so this cluster must have been specified in the `app-config.yaml`, under the Kubernetes clusters configuration (for more details, see [`Configuring Kubernetes clusters`](#configuring-kubernetes-clusters)).
If you do not specify the annotation by `default Backstage fetches all` defined Kubernetes cluster.
If you do not specify the annotation, by default Backstage fetches from all defined Kubernetes clusters.
[1]: https://cloud.google.com/kubernetes-engine
[2]: https://cloud.google.com/docs/authentication/production#linux-or-macos