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!! 

[Adz1]

Workaround found and confirmed working on AWS.

@Deepanshu Grover - please test the following with Azure to see if you can replicate the fix.

Add the SSL Certificate to the MID server using Add SSL certificates for the MID Server | ServiceNow Docs

Note that the command I used to install the cert (on a linux mid server) was 
./keytool -import -alias aws-kubes -file "aws-kubes.cer" -cacert 

The password for the keystore is changeit

[Deepanshu Grov1]

Great, let me also try the same at my end too, do you have some phone number, if I can have a quick call with you for 2 minutes on the same topic. 

Thanks

Deepanshu Grover

[Adz1]

I've sent you an invite on LinkedIn, let's arrange a call on from there. 

[Deepanshu Grov1]

how do we get this password, I mean from where?

[Adz1]

Found it here: 

MID Web Server mTLS Authentication | ServiceNow Docs 

and 

The fix for PRB1320637 requires that the cacerts Truststore file password remains as the default "ch...