Upgrading Telemetry Collector

This article outlines the procedure for upgrading a Telemetry Collector

Instructions are provided for Kubernetes and Docker.

How to check if existing Telemetry Collectors require software upgrade

The release notes will indicate if a new version of the Telemetry Collector is available:

• On Premise Continuous Controlled Availability release
• Cloud Continuous Controlled Availability release

If there is a new version of the Telemetry Collector for the software release you are using, you can follow the instructions below to perform the upgrade.

Upgrade Procedure: Docker Environment

Upgrade Procedure: Kubernetes Environment

To upgrade a Telemetry Collector in a Kubernetes environment:

Step 1. Retrieve Telemetry Collector Helm Charts (Required only for Air gapped deployments)

Since air gapped deployments can not access the internet to retrieve Helm charts, this step must be done manually. For environments with access to the internet, proceed to step 2.

Download the Telemetry Collector helm charts to a local file and transfer to the working directory on the machine where you configure your Kubernetes cluster via helm.

telemetry-collector-ca.tgz

Step 2. Retrieve The Telemetry Collector Docker Image (Required only for Air gapped deployments)

Download the docker image for the Telemetry Collector to a local file and transfer to the working directory on the machine where you configure your Kubernetes cluster via helm.
Command for pulling the image:

docker pull gcr.io/sky-agents/agent-telemetry-amd64:ca

Example for saving image to a file:

docker save -o agent-telemetry-amd64-ca.tar gcr.io/sky-agents/agent-telemetry-amd64:ca

Load the saved docker image into the helm machine's local docker registry.
Example:

docker load -i agent-telemetry-amd64-ca.tar

Step 3. Import The Telemetry Collector Image Into The Kubernetes Cluster

The Telemetry Collector docker image must be uploaded to the Kubernetes cluster's OCI registry. If you're using the Provider Connectivity Assurance Kubernetes cluster, you can follow the example below. If you're using your own registry, you must upload the image to it.

Example:

kubectl get secret kotsadm-replicated-registry -n pca -o jsonpath='{.data..dockerconfigjson}' | base64 -d
{"auths":{"10.244.128.11:5000":{"auth":"ZW1iZWRkZWQtY2x1c3RlcjpsRFVkTWRqZjg5dWlGcHV6ODBvQQ=="}}}

In this case 10.244.128.11:5000 is the address of our internal registry.  We will use that below.

Decode the Base64 from the previous response to get our authentication credentials:
Example:

echo 'ZW1iZWRkZWQtY2x1c3RlcjpsRFVkTWRqZjg5dWlGcHV6ODBvQQ==' | base64 -d
embedded-cluster:lDUdMdjf89uiFpuz80oA

Use the extracted address and credentials to log into the docker registry.
Example:

docker login 10.244.128.11:5000 -u embedded-cluster -p lDUdMdjf89uiFpuz80oA

Re-tag the Telemetry Collector image for the PCA cluster's internal registry.
Example:

docker tag gcr.io/sky-agents/agent-telemetry-amd64:ca 10.244.128.11:5000/pca-dev/agent-telemetry-amd64:ca

Push the re-tagged image to the PCA cluster's internal registry:
Example:

docker push 10.244.128.11:5000/pca-dev/agent-telemetry-amd64:ca

Step 4. Install The Telemetry Collector

Helm install the Telemetry Collector, referencing the locally pulled chart and the values.yaml file that you just created.
Example:

helm upgrade telemetry-collector ./telemetry-collector-ca.tgz -f ./values.yaml -n cisco-sensor-collectors