Kubernetes Discovery

suresh90
Kilo Contributor

HI Team,

Does anyone implemented kubernetes discovery  and open shift components.

Could you please share me the steps how to make to discovery successful.

I got the credentials I'm paused at creating  Serverless discovery schedules .

 

Thanks & Regards,

Suresh.

 

 

 

7 REPLIES 7

knoxkf
Kilo Guru

Hi Suresh - I successfully discovered 1 k8 device.  I had to open a HI ticket to get it working though.  We are also on the newer version of K8 (.15) while ServiceNow is only supported up to .10.  The issue we had was related to the credential setup but once we sorted that it worked...  we are still trying to decipher what was discovered.

suresh90
Kilo Contributor

HI Knoxf,

 

Thanks for the email.

 

could you please let me know how you have setup discovery schedule for Kubernetes.

as per docs needs to create serverless discovery, i'm confused where to add Ip with port number to discovery them.

 

Thanks & Regards,

Suresh.
 

Severin Launiau
Giga Guru

Hi Suresh,

 

I posted on a similar thread a while back: https://community.servicenow.com/community?id=community_Question&sys_id=5b43fc341b6d4418d01143f6fe4bcb0d

 

So for me:

Discovery - Credentials: one record for each OCP cluster with:

- type = sn_itom_pattern_kubernetes

- bearer_token_authentication set to true

- bearer_token assigned to whatever our Infrastructure team provided for that cluster

- active set to true

- credential alias: some name I made up to identify the cluster, i.e. us_east_prod

 

Discovery Schedules: one schedule for each OCP cluster with:

- Discover: Serverless

- Credential Alias: shouldn't be needed at this point

- Serverless Execution Patterns: one and only one record for that schedule: pattern Kubernetes, active set to true; and then for that execution pattern launcher, 3 parameters:

- credentials alias => same as for the creds associated with your cluster, i.e. us_east_prod

- url => https://manage.${your_ocp_url}:443/api/v1

- namespace => *

 

Let me know how that worked!

 

Séverin

I have tried the same and am getting the 401 credential error, I am able to login to my service account in OC client and genrate token but not sure why i am getting the error