Azure: Kubernetes cluster name in SN not match with actual name in Azure

[Nattaphol Ubols]

HI folks, 

Hope you can assist me on this query. We have Azure and Kubernetes discovery running. We discovery aks clusters as expected however the cluster names got populated slightly different from the actual name in Azure

for example:

name in Azure ; nxs-dev-pg004-euno-aks

name in cmdb : Kubernetes Cluster nxs-dev-pg004-euno-aks-xxxxxx.xxx.northeurope.xxxxx.io:443

this seems to be from the kubernetes event discovery pattern but i'm not so sure what step that does this?

can I configure it to populate the actual cluster name?

[Community Alums]

hi @Nattaphol Ubols , we are facing the same issue. i have modified the pattern extension to populate the actual name but then whenever azure cloud resource subscription discovery runs. The value in the name field is getting overridden. I will keep posted here. if i find any solution for this issue

Regards, 

Srinija

[Chitra23]

We are facing the same issue. Any updates on this?

[srinija_itom]

Hi @Chitra23, 

Here  is the approach we implemented in order to override the name issue. Azure cloud discovery was brining up name in a different format and Kubernetes schedules was brining up a name in different format. 

In order to fix this issue, we created a pattern extension step to populate the name field in correct format. 

Verify the ci identifiers on the Kubernetes cluster table, try to find a common field between both the discoveries so that values doesn’t flap when both type of discoveries run. 

Regards, 

Srinija