Kuberenets Discovery

[Ansuman Giri]

I am trying to set up a Kubernetes discovery as a part of a project, 
I have created Kubernetes credentials with bearer token and added them to a credential alias. 
created a serverless discovery Schedule  as per the doc( https://docs.servicenow.com/bundle/quebec-it-operations-management/page/product/service-mapping/concept/kubernetes-discovery.html)

when I run the discovery I am getting the error 
Kubernetes Namespace API call failed or there are no Namespaces in the query. Please verify the configuration data and/or user permissions., Pattern name: Kubernetes, To Check Pattern Log Navigate to:...

but I have already mentioned * as a namespace 

When I am debugging the Kubernetes patten at get namespace step I am getting the error below:

 "Failed to retrieve remote data: Custom operation Kubernetes Get Call failed to execute script due to Custom operation Failed to run script due to the following error: JAVASCRIPT_CODE_FAILURE: Cannot convert null to an object. Check the discovery logs for more details."

I am not getting it where am I doing wrong, Please help!! 

[Shoheb_IbaaBoss]

Hello,

We are also facing the namespace issue for one of the Kubernetes cluster to be discovered. 

We are using namespace as * and it did not worked. We tried with "default" provided by team but still no luck. Below is the message that we get in logs:

Pattern exit because Graceful Termination, reason: Kubernetes Namespace API call failed or there are no Namespaces in the query. Please verify the configuration data and/or user permissions. Failed Condition(s): [(${namespaces[*].k8s_uid} : value=[]) IS NOT EMPTY ]

Other Kubernetes clusters got discovered using the namespace as * but this one we are facing the challenge.

How do I resolve this issue?

Regards,

Shoheb

[devpc]

Hi, there is a solution for this? @Hail  @Deepanshu Grov1  @Adz1  @Shoheb_IbaaBoss  @Ansuman Giri  

I'm facing the same issue