Itom Discovery: Kubernetes on Azure, serverless pattern parameters - Support and Troubleshooting

Itom Discovery: Kubernetes on Azure, serverless pattern parameters Issue .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: ; } } After running discovery on an Azure subscription the Kubernetes discovery schedule is automatically created, but fails on the 'url' parameter being empty. When doing on-prem Kubernetes discovery this url points to the Kube-API server. In the automatically created schedule for Kubernetes on Azure this parameter is empty. Should it be filled in, automatically be filled in, manually updated?

Release .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: ; } } all releases

Resolution .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: ; } } In the Serverless Execution Patterns tab > open "Serverless Execution Pattern > correct the 'url' with including hostname, IP, or FQDN and the port of the Kubernetes apiserver.

NOTE: The automatic schedule creation for Kubernetes discovery on Azure is only partially functional. Some parameters are to be filled in, before it becomes a working schedule

Current Behavior 1. When running discovery on an Azure subscription, ServiceNow automatically creates a Kubernetes discovery schedule 2. However, this automatically created schedule has an empty 'url' parameter 3. This parameter is critical as it should point to the Kubernetes API server 4. Without this parameter properly configured, the discovery fails

Expected vs. Actual Behavior

Expected: The automatic schedule creation should populate all necessary parameters, including the 'url' parameter Actual: The 'url' parameter is left empty (or with just "https://") and requires manual intervention

Required Manual Configuration You need to:

1. Navigate to the Serverless Execution Patterns tab 2. Open "Serverless Execution Pattern 3. Manually correct the 'url' parameter by adding the hostname, IP, or FQDN and the port of the Kubernetes API server

This appears to be a limitation in the current implementation of the Azure Kubernetes discovery process. While ServiceNow can automatically detect the presence of Kubernetes clusters in Azure and create discovery schedules for them, it cannot automatically determine the API server endpoint that's needed for the discovery to function properly.

You should proceed with manually updating the 'url' parameter as suggested in the solution. This will enable the discovery schedule to function correctly and discover the Kubernetes resources in their Azure environment.

Also, you would need to configure the attributes "Configuring execution pattern attributes" in the following documentation. https://docs.servicenow.com/bundle/tokyo-it-operations-management/page/product/service-mapping/concept/kubernetes-discovery.html

According to the documentation, there are specific attributes that need to be configured for the Kubernetes discovery execution pattern to work properly which aligns with the issue where the automatically created schedule has an empty 'url' parameter.

Key Attributes to Configure The execution pattern attributes that need to be configured include:

1. URL - This is the critical parameter missing. It should point to the Kubernetes API server (e.g., https://kubernetes.example.com:6443). 2. Namespace - Specifies which Kubernetes namespaces to discover. The default value is "*" which discovers all namespaces. 3. Provider - Indicates the cloud provider (AZURE in your case). 4. Cluster Name - Identifies the specific Kubernetes cluster. 5. Credentials Alias - References the credentials to use for authentication. 6. Prometheus URL - Optional URL for Prometheus metrics integration.

Steps to Configure the Execution Pattern

1. Navigate to the Serverless Execution Patterns tab. 2. Open the specific pattern "Serverless Execution Pattern". 3. Update the 'url' parameter with the complete address of your Kubernetes API server, including: Protocol (https://) Hostname/IP/FQDN Port (typically 443 or 6443) 5. Verify other attributes like namespace, provider, and cluster_name are correctly populated. 6. Save the configuration.

Finding the Kubernetes API Server URL

For Azure Kubernetes Service (AKS), you can find the API server URL through:

1. Azure Portal: Navigate to your AKS cluster → Overview → Kubernetes resource → API server address 2. Azure CLI: Use az aks show -g -n --query fqdn -o tsv

Once configured correctly with the proper URL, the discovery schedule should successfully connect to your Kubernetes cluster and perform the discovery process.

Apply the URL with the given information