Documentation forSolarWinds Observability

Upgrade Kubernetes monitoring

On January 18, 2023, SolarWinds Observability made significant improvements within the Kubernetes observability features. To see the latest enhancements and avoid an incomplete view of the data in your dashboards, upgrade your cluster to the latest version of the SolarWinds Observability k8s collector.

Determine if you need to upgrade your cluster

If a Kubernetes entity was added to SolarWinds Observability prior to January 18, 2023, you must upgrade your collector to manifest version 2.0. The collector and manifest are now deployed with a Helm chart.

Upgrade your existing Kubernetes cluster

To upgrade your Kubernetes cluster deployment while maintaining the history of the cluster's metrics and logs, manually update your existing Kubernetes cluster.

  1. Identify the UID of the Kubernetes cluster: 

    1. Locate your Kubernetes cluster in the Entity Explorer.

    2. Click on the cluster to view the entity details page.

    3. Find the UID of the Kubernetes cluster in the Details widget.

  2. Remove the existing Kubernetes configuration using one of the following methods:

    • If you still have the manifest.yaml file used to deploy the SolarWinds Observability k8s collector, use the following command to remove the cluster configuration. Replace <NAMESPACE> with the namespace where you installed the SolarWinds Observability k8s collector.

      kubectl delete -f manifest.yaml -n <NAMESPACE>
    • If you no longer have the manifest.yaml file used to deploy the SolarWinds Observability k8s collector, delete each deployed resource individually with the following commands. Replace <NAMESPACE> with the namespace where you installed the SolarWinds Observability k8s collector.

      kubectl delete deployment -n <NAMESPACE> swi-opentelemetry-collector
      kubectl delete daemonset -n <NAMESPACE> swi-opentelemetry-collector-logs
      kubectl delete serviceaccounts -n <NAMESPACE> swi-opentelemetry-collector
      kubectl delete clusterrolebindings swi-opentelemetry-collector
      kubectl delete clusterrole swi-opentelemetry-collector
      kubectl delete secret -n <NAMESPACE> solarwinds-api-token
  3. Re-add your Kubernetes cluster as a new entity with the Add Data dialog. See Add a Kubernetes cluster.
  4. Add the cluster UID identified in step 1 to the values.yaml file:

    cluster: 
      name: … 
      uid: <cluster UID>

    For additional setup options, see all the configuration options in the sample values.yaml.

Verify all of your organization's clusters are upgraded

To verify that all of your Kubernetes clusters have been upgraded to manifest version 2.0, use the Metrics Explorer to view the manifest version that was used to send the most recent data to SolarWinds Observability.

After your clusters have sent data to SolarWinds Observability, open the Metrics Explorer. View the k8s.kube_pod_info metric, using the time period filter to show data from the last hour, aggregating by count, and grouping by the sw.k8s.agent.manifest.version and k8s.cluster.name tags. The result will be a list of each Kubernetes cluster that is sending data for your organization and the corresponding manifest version.