Kubernetes Cluster CI naming format when leader node detection failsSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: 'Lato', sans-serif; font-size: 12pt; line-height: 1.7; color: #1d1d1d; max-width: 100%; } .kb-wrapper h3 { font-family: 'Lato', sans-serif; font-size: 12pt; font-weight: 900; color: #032D42; border-bottom: 2px solid #e8fce4; padding-bottom: 4px; margin-top: 20px; margin-bottom: 8px; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper code { background-color: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; border-radius: 3px; padding: 1px 5px; font-family: 'Courier New', Courier, monospace; font-size: 11pt; } .kb-wrapper pre { background-color: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; border-radius: 4px; padding: 12px 16px; overflow-x: auto; margin: 12px 0; } .kb-wrapper pre code { background: none; border: none; padding: 0; font-size: 11pt; } During Kubernetes Discovery, you might see configuration items (CIs) in the Kubernetes Cluster [cmdb_ci_kubernetes_cluster] table created with names in the format “Kubernetes Cluster <Host IP>:<Port>”. This article explains when and why Discovery generates names in this format. The Kubernetes pattern sets the name attribute on the Kubernetes Cluster [cmdb_ci_kubernetes_cluster] CI using the following logic, applied in order. Step 1 — Leader node API call Discovery makes a leader node API call to the following endpoint: https://<url>/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?limit=50 If successful, the retrieved value populates the $master_node_name variable and sets the CI name. Step 2 — Cluster Name from discovery schedule (failover) If the leader node call fails, Discovery uses the Cluster Name value from the discovery schedule configuration, provided in the following format: <serviceaccountid> <clustername> For more information on the discovery schedule configuration, see “Configuring execution pattern attributes” in the documentation listed in Related Links. Step 3 — Generated name (final failover) If no Cluster Name is set in the discovery schedule configuration, Discovery generates the CI name using the following formula: "Kubernetes Cluster " + $host + ":" + $port The “Kubernetes Cluster” prefix in a CI name indicates that both the leader node API call and the Cluster Name lookup failed, and that Discovery generated a best-effort name. CIs with this naming format can be used to identify that the discovery schedule configuration or cluster endpoint may need attention. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } .kb-wrapper { font-family: 'Lato', sans-serif; font-size: 12pt; line-height: 1.7; max-width: 100%; } .kb-wrapper ul { list-style: none; padding: 0; margin: 0; } .kb-wrapper li { margin-bottom: 8px; } .kb-wrapper a { color: #032D42; } Kubernetes Discovery using patterns