Upgrade CNO for Visibility

  • Release version: Washingtondc
  • Updated January 12, 2025
  • 3 minutes to read
  • You can upgrade CNO for Visibility using either a Helm chart or the Kubernetes YAML file.

    Before you begin

    Role required: none

    About this task

    This procedure describes the standard CNO for Visibility upgrade process. Typically, you would use a Helm chart to perform the upgrade. Alternately, you can upgrade CNO for Visibility by configuring and running the Kubernetes YAML file provided by ServiceNow. In both cases, there is no need to uninstall before upgrading.

    You can also upgrade CNO for Visibility Informer pods in Kubernetes clusters remotely from the ServiceNow Instance. For more information, see Upgrade Agent Client Collector for Kubernetes – Visibility Informers remotely.

    Procedure

    Upgrade CNO for Visibility using either a Helm chart or the Kubernetes YAML file provided by ServiceNow.
    • Upgrade CNO for Visibility using a Helm chart.

      1. Edit the Helm upgrade command.
        1. 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.
          helm upgrade -n NAMESPACE --set acceptEula=Y --set instance.name=INSTANCE_NAME --set clusterName="CLUSTER_NAME" {--set image.repository=COMPANY_REPO --set image.tag=COMPANY_TAG} {--set proxyUrl=http://proxy_host:proxy_port} k8s-informer HELM_URL
          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:
            helm upgrade -n NAMESPACE --set acceptEula=Y --set instance.name=INSTANCE_NAME --set clusterName="CLUSTER_NAME" {--set image.repository=COMPANY_REPO --set image.tag=COMPANY_TAG} {--set proxyUrl=http://proxy_host:proxy_port} {--set openShift=true} k8s-informer HELM_URL
            Note:
            If the Informer is not installed in OpenShift, there is no need to set this parameter.
        2. In the command, configure additional settings as needed:
      2. Run the command.
    • Upgrade CNO for Visibility using the Kubernetes YAML file.
      1. 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.
      2. Extract the k8s_informer.yaml and EULA.pdf files from the zip file.
      3. Edit the k8s_informer.yaml file.
        • Change the value of ACCEPT_EULA to "Y", as follows:
          - name: ACCEPT_EULA
            value: "Y"
          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.
      4. Run the command:
        kubectl apply -f k8s_informer.yaml

    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.