Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
It configures the MID Server name used for discovering Kubernetes clusters in cloud environments, facilitating effective integration with cloud services. |
| What area does it affect? |
Discovery and Service Mapping |
| What does the default mean? |
No default value is documented in this property record. |
| When should you review it? |
An admin should review this property when setting up cloud discovery for Kubernetes or when changing the MID Server configuration. |
Out of the box property record
Raw metadata from the property record.
| Property name |
sn_itom_pattern.k8s_midserver |
| Sys ID |
afae61a11b6909108fad9868b04bcb2d |
| Type |
string |
| Application |
Discovery and Service Mapping Patterns |
| Default value |
|
| Description |
Mid Server name, deployed in cloud |
| Updated |
2022-02-15 04:35:19 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... to "Allow full access to all Cloud APIs". The MID Server instance can access only the Clusters specific to the project. 3. Navigate to sys_properties.list and configure the following properties: ◦sn_itom_pattern.k8s_midserver: Specify a valid MID Server name. ◦sn_itom_pattern.k8s_create_schedule_enabled: Set the value to true. Note: Enabling the sn_itom_pattern.k8s_create_schedule_enabled property automatically creates a serverless schedule for your cloud clusters, eliminating the need for ...