question Kubernetes Discovery Issue in ITOM forum

Kubernetes Discovery Issue

Deepanshu Grov1 — Tue, 08 Mar 2022 11:18:42 GMT

Hi,

I am trying to run the Kubernetes Discovery, however, getting the following error:

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.

I already have tested the connectivity of this API from the mid server using the postman and it is working fine. 
Any assistance around this topic will be highly appreciated. 


Thanks

Deepanshu Grover
+47-46634388

Re: Kubernetes Discovery Issue

BobinV — Tue, 08 Mar 2022 11:35:45 GMT

Hi Deepanshu,

Could you let us know what value you have provided under "namespace" parameter in the Discovery Schedule >Serverless Execution Patterns > Discovery Pattern Launcher Parameters"?

If you have given a specific value, it will look for that specific namespace. if you want to discover the entire cluster give *.

Thanks,

Bobin

Re: Kubernetes Discovery Issue

Deepanshu Grov1 — Tue, 08 Mar 2022 11:40:57 GMT

I have given (*) in the namespace and I have also tried giving default there, same result I get...

Re: Kubernetes Discovery Issue

BobinV — Tue, 08 Mar 2022 11:53:12 GMT

Hi,

Can you refer the below KB and check under Kuberenetes link if anything is useful.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0859915#mcetoc_1ej37fdtegq

Would be interesting to know what resolved the issue.

Thanks,

Bobin

Re: Kubernetes Discovery Issue

jamesmillet — Mon, 02 May 2022 20:38:38 GMT

Any resolution to this issue? I am getting the SAME error. I am using * for the namespace.

Re: Kubernetes Discovery Issue

Deepanshu Grov1 — Tue, 03 May 2022 11:22:02 GMT

Hey, I have successfully resolved that error, are you discovering Azure AKS...

Please ensure that you have ports opened from mid server to azure AKS clusters URL and bearer token is right.

You can test the same by installing the postman on the mid server itself and then try to GET the API.

You might need to disable the SSL cert there in the Postman if you do not have the right certificate at the moment, try that first and share your response.

Re: Kubernetes Discovery Issue

pratiksha5 — Wed, 27 Sep 2023 07:39:54 GMT

how to get the token. I am not able to find the correct command.