Install CNO for Visibility
-
- UpdatedFeb 1, 2024
- 4 minutes to read
- Washington DC
- IT Operations Management
You can install Cloud Native Operations for Visibility using either a Helm chart or the Kubernetes YAML file.
Before you begin
CNO for Visibility detects changes on resources in a Kubernetes cluster and updates the appropriate tables in the CMDB. For more information, see Using Cloud Native Operations for Visibility.
Role required: none
About this task
Procedure
-
Install CNO for Visibility using a Helm chart.
- Edit the Helm install command.
- In the following command, replace NAMESPACE, INSTANCE_NAME, and CLUSTER_NAME with the relevant values and replace the HELM_URL with the URL of the most recent version, provided in the CNO for Visibility Helm Chart and Kubernetes YAML file releases [KB1564347] article in the Now Support Knowledge Base.Note:
- The curly brackets indicate that the code segments they surround are optional. Use these code segments if the image must be pulled from your organization’s image repository or if outgoing traffic from your cluster flows through a proxy.
- By passing
--set acceptEula=Y
, you agree to the End-User License Agreement. You can read the End-User License Agreement by extracting the EULA.pdf from informer-helm-<VERSION_NUMBER>.tgz. - If the Informer is installed in OpenShift, add the openShift parameter to the command and set it to true:Note: If the Informer is not installed in OpenShift, there is no need to set this parameter.
- In the command, configure additional settings as needed:
- Configure the memory limit of the Informer pod
- Change the full discovery frequency in CNO for Visibility
- Deactivate continuous discovery in CNO for Visibility
- Suppress frequent changes in the Kubernetes cluster to reduce the load on your instance. When this feature is active, the Informer does not report changes above the configured threshold rate back to the instance. For more information, see the Suppressing frequent changes in Kubernetes clusters reported by CNO for Visibility [KB1580745] article in the Now Support Knowledge Base.
- Control the maximum number of full discoveries that informers can run on multiple clusters at the same time. For more information, see the Scheduling Full Discoveries in CNO for Visibility [KB1580250] article in the Now Support Knowledge Base.
- In the following command, replace NAMESPACE, INSTANCE_NAME, and CLUSTER_NAME with the relevant values and replace the HELM_URL with the URL of the most recent version, provided in the CNO for Visibility Helm Chart and Kubernetes YAML file releases [KB1564347] article in the Now Support Knowledge Base.
- Run the command.
- Edit the Helm install command.
- Install CNO for Visibility using the Kubernetes YAML file.
- Download the Kubernetes YAML zip file provided in the CNO for Visibility Helm Chart and Kubernetes YAML file releases [KB1564347] article in the Now Support Knowledge Base.
- Extract the k8s_informer.yaml and EULA.pdf files from the zip file.
- Edit the k8s_informer.yaml file.
- Change the value of ACCEPT_EULA to "Y", as follows:Note: By changing the value to "Y", you agree to the End-User License Agreement included in the EULA.pdf file.
- Replace all occurrences of <NAMESPACE> with the namespace in which you want to install the Informer.
- Replace all occurrences of <INSTANCE_NAME> with the name of your instance, without the domain name.
- Replace <CLUSTER_NAME> with the name of your cluster as it appears in the CMDB.
- If the Informer is installed in OpenShift, change the value of the OPENSHIFT environment variable to true.
- Change the value of ACCEPT_EULA to "Y", as follows:
- Run the command:
Result
CNO for Visibility is deployed on the Kubernetes cluster and begins to stream data into your instance.
What to do next
For information about CNO for Visibility administration and troubleshooting, see the Administrating and Troubleshooting CNO for Visibility (Cloud-Native-Operations) [KB1532614] article in the Now Support Knowledge Base.