From 43c757ae6080931b63ea7001aac45aedf2a35403 Mon Sep 17 00:00:00 2001 From: Gazandi Date: Thu, 4 Mar 2021 20:30:39 +0700 Subject: [PATCH] Update troubleshooting.md Signed-off-by: gazandi --- docs/features/kubernetes/troubleshooting.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/features/kubernetes/troubleshooting.md b/docs/features/kubernetes/troubleshooting.md index 1fac1f1ece..882c6f03f6 100644 --- a/docs/features/kubernetes/troubleshooting.md +++ b/docs/features/kubernetes/troubleshooting.md @@ -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: ` and `backstage.io/kubernetes-id: `.