2017-05-05 05:24:04 +00:00
---
2020-04-07 18:55:19 +00:00
layout: docs
page_title: Consul Enterprise Automated Upgrades
description: >-
Consul Enterprise supports an upgrade pattern that allows operators to deploy
a complete cluster of new servers and then just wait for the upgrade to
complete.
2017-05-05 05:24:04 +00:00
---
2020-03-24 20:06:20 +00:00
# Automated Upgrades
2017-05-05 05:24:04 +00:00
2020-04-23 22:13:18 +00:00
<EnterpriseAlert>
2021-12-10 22:42:33 +00:00
This feature requires
HashiCorp Cloud Platform (HCP) or self-managed Consul Enterprise.
Refer to the{' '}
2022-04-27 16:25:16 +00:00
<a href="/docs/enterprise#consul-enterprise-feature-availability">enterprise feature matrix</a>
2022-04-27 16:45:30 +00:00
{' '}for additional information.
2020-04-23 22:13:18 +00:00
</EnterpriseAlert>
Consul Enterprise enables the capability of automatically upgrading a cluster of Consul servers to a new
2020-04-06 20:27:35 +00:00
version as updated server nodes join the cluster. This automated upgrade will spawn a process which monitors the amount of voting members
currently in a cluster. When an equal amount of new server nodes are joined running the desired version, the lower versioned servers
will be demoted to non voting members. Demotion of legacy server nodes will not occur until the voting members on the new version match.
Once this demotion occurs, the previous versioned servers can be removed from the cluster safely.
2020-03-24 20:06:20 +00:00
2022-09-06 15:35:01 +00:00
Review the [Consul operator autopilot](/commands/operator/autopilot) documentation and complete the [Automated Upgrade](https://learn.hashicorp.com/tutorials/consul/autopilot-datacenter-operations#upgrade-migrations) tutorial to learn more about automated upgrades.
