TELEMETRY PIPELINE
Install
Upgrade

Upgrade Chronosphere Telemetry Pipeline

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

Upgrade Core Operators and Core Instances

These steps upgrade Core Operator and Core Instance to the latest available version. 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.

  1. 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.

  2. Run the following command to install the latest version of Core Operator, which overwrites any previously installed versions:

    calyptia install operator

    Optionally, you can use the --kube-namespace flag to set the Core Operator's namespace.

  3. 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 the following command in 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 upgrade.
  • VERSION: The latest version of the pipeline agent.

Deployment strategies

When you upgrade a pipeline, you can specify its deployment strategy, which governs how that pipeline's replicas behave during the upgrade process. To do so, use the following command:

calyptia update pipeline PIPELINE \
	--image ghcr.io/calyptia/core/calyptia-fluent-bit:VERSION \
	--deployment-strategy=OPTION

Replace the following:

  • PIPELINE: Either the name or unique ID of the pipeline you want to upgrade.
  • VERSION: The latest version of the pipeline agent.
  • OPTION: The deployment strategy you'd like to use. These values are case sensitive.
    • rollingupdate: Default. Individually restarts each replica of a pipeline. If a a pipeline only has one replica, this strategy creates a new replica before restarting the existing replica.
    • hotReload: Upgrades all of a pipeline's replicas simultaneously, without restarting any of them.
Linux troubleshootingUninstall