HashiCorp Learn
Infrastructure
  • TerraformTerraformLearn terraformDocs
  • PackerPackerLearn packerDocs
  • VagrantVagrantLearn vagrantDocs
Security
  • VaultVaultLearn vaultDocs
  • BoundaryBoundaryLearn boundaryDocs
Networking
  • ConsulConsulLearn consulDocs
Applications
  • NomadNomadLearn nomadDocs
  • WaypointWaypointLearn waypointDocs
  • HashiCorp Cloud Platform (HCP) LogoHashiCorp Cloud Platform (HCP)HashiCorp Cloud Platform (HCP)Docs
Type '/' to Search
Loading account...
  • Bookmarks
  • Manage Account
  • Overview
DocsForum
Back to nomad
Job UpdatesView Collection
    Nomad Job Update StrategiesRolling UpdatesBlue/Green & Canary DeploymentsConfigure Exit Signals for Jobs

Nomad Job Update Strategies

  • 1 min
  • Products Usednomad

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

Start with one of the tutorials below or use the navigation on the left:

  • Rolling Updates
  • Blue/Green & Canary Deployments
  • Handling Signals


Back to Collection
HashiCorp
  • System Status
  • Terms of Use
  • Security
  • Privacy
stdin: is not a tty