Pipeline deployment strategies
Deployment strategies govern how a pipeline’s replicas behave during the upgrade process. Chronosphere Telemetry Pipeline offers these deployment strategies:
- Rolling Update: Default. Individually upgrades and restarts each replica of a pipeline. This ensures that at least one replica is always running, which lets telemetry data continue to flow without interruption. If a pipeline has only one replica, this strategy creates a new, upgraded replica, and then destroys the old replica.
- Hot Reload: Upgrades all of a pipeline’s replicas simultaneously without restarting any of them. During this upgrade process, pipelines continue to run and they attempt to maintain the flow of telemetry data.
Modify a pipeline’s deployment strategy
Use one of these methods to modify a pipeline’s deployment strategy.
- Sign in to Telemetry Pipeline (opens in a new tab).
- Open the project that contains the pipeline whose deployment strategy you want to modify.
- Go to Core Instances, and then click the name of the Core Instance associated with the pipeline whose deployment strategy you want to modify.
- In the Data Pipelines section, click the name of the pipeline whose deployment strategy you want to modify.
- Click Advanced Settings.
- In the Deployment Strategy section, select either Rolling Update or Hot Reload.
- To save your changes, click Update.