Upgrade Chronosphere Telemetry Pipeline

Upgrading the various components of Chronosphere Telemetry Pipeline gives you access to the latest features, fixes, and improvements.

Active pipelines continue to run during the upgrade process, but might need to restart. Telemetry Pipeline uses a rolling restart (opens in a new tab) method that either individually restarts each replica of a pipeline or, if a pipeline only has one replica, creates a new replica before restarting the existing replica.

Upgrade Core Operator and Core Instance

These steps upgrade Core Operator and Core Instance to the latest available version. To upgrade Core Operator and Core Instance, use the same method that you originally used to install them.

If you deployed Telemetry Pipeline inside a Kubernetes cluster, Pipeline CLI must have access that cluster. If you deployed Telemetry Pipeline on a Linux server, you must run Pipeline CLI from inside that server environment.

Update Pipeline CLI. Because Core Instance versions are dependent on your Pipeline CLI version, the latest version of Pipeline CLI installs the latest version of Core Instance.
Run the following command to install the latest version of Core Operator, which overwrites any previously installed versions:
```
calyptia install operator
```
Run the following command to update Core Instance:
```
calyptia update core_instance operator INSTANCE
```
Replace INSTANCE with the name of the Core Instance you want to update.

Upgrade a pipeline

To upgrade an existing pipeline, use Pipeline CLI:

calyptia update pipeline PIPELINE --image ghcr.io/calyptia/core/calyptia-fluent-bit:VERSION

Replace the following:

PIPELINE: Either the name or unique ID of the pipeline you want to modify.
VERSION: The latest version of the Core Instance.

Helm Uninstall