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

Update troubleshooting.md

Browse Source 
Signed-off-by: gazandi <gazandi@ruangguru.com>
This commit is contained in:
Gazandi
2021-03-04 20:30:39 +07:00
committed by gazandi
parent 3b2312b8a8
commit 43c757ae60
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/kubernetes/troubleshooting.md
+5 -5
View File
@@ -7,8 +7,8 @@ description: Troubleshooting for Kubernetes
## Kubernetes is not showing up on Service Entities
Sometimes, Kubernetes is not showing up on service entities, we should test your
k8s cluster are already connected to Backstage or not.
This can be debugged by checking whether your Kubernetes cluster are
connected to Backstage as follows:
```curl
curl --location --request POST '{{backstage-backend-url}}:{{backstage-backend-port}}/api/kubernetes/services/:service-entity-name' \
@@ -67,9 +67,9 @@ The curl response should have resources from Kubernetes:
```
Kubernetes will not be showing anything when catalog info annotations is not
match with k8s related yaml label (service.yaml, deployment.yaml, etc). We
recommend you for adding two labels and using label selector annotations:
The Kubernetes tab will not show anything when the catalog info annotation does not
match the related Kubernetes resource. We recommend you add the following labels to
your resources and use the label selector annotation as follows:
`backstage: <selector>` and `backstage.io/kubernetes-id: <entity-service-name>`.