2016-10-12 00:15:30 +00:00
|
|
|
---
|
2018-04-18 22:18:23 +00:00
|
|
|
layout: "guides"
|
2016-10-12 00:15:30 +00:00
|
|
|
page_title: "Update Strategies - Operating a Job"
|
2018-04-18 22:18:23 +00:00
|
|
|
sidebar_current: "guides-operating-a-job-updating"
|
2016-10-12 00:15:30 +00:00
|
|
|
description: |-
|
|
|
|
|
This section describes common patterns for updating already-running jobs
|
|
|
|
|
including rolling upgrades, blue/green deployments, and canary builds. Nomad
|
|
|
|
|
provides built-in support for this functionality.
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Update Strategies
|
|
|
|
|
|
|
|
|
|
Most applications are long-lived and require updates over time. Whether you are
|
|
|
|
|
deploying a new version of your web application or upgrading to a new version of
|
2017-07-26 22:06:17 +00:00
|
|
|
Redis, Nomad has built-in support for rolling, blue/green, and canary updates.
|
|
|
|
|
When a job specifies a rolling update, Nomad uses task state and health check
|
|
|
|
|
information in order to detect allocation health and minimize or eliminate
|
|
|
|
|
downtime. This section and subsections will explore how to do so safely with
|
|
|
|
|
Nomad.
|
2016-10-12 00:15:30 +00:00
|
|
|
|
|
|
|
|
Please see one of the guides below or use the navigation on the left:
|
|
|
|
|
|
2018-04-18 22:18:23 +00:00
|
|
|
1. [Rolling Upgrades](/guides/operating-a-job/update-strategies/rolling-upgrades.html)
|
|
|
|
|
1. [Blue/Green & Canary Deployments](/guides/operating-a-job/update-strategies/blue-green-and-canary-deployments.html)
|
|
|
|
|
1. [Handling Signals](/guides/operating-a-job/update-strategies/handling-signals.html)
|
