9074778c0c
* fixing links in the docs post guide migartion. * fixed one more * Update website/source/docs/acl/acl-legacy.html.md Co-Authored-By: kaitlincarter-hc <43049322+kaitlincarter-hc@users.noreply.github.com> * Update website/source/docs/enterprise/connect-multi-datacenter/index.html.md * Updating based on comments and fixing word wrap * Update website/source/api/acl-legacy.html.md * Update website/source/api/acl/acl.html.md * Update website/source/docs/agent/options.html.md * Update website/source/docs/faq.html.md * Update website/source/docs/internals/architecture.html.md * Update website/source/docs/agent/encryption.html.md
20 lines
1 KiB
Markdown
20 lines
1 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Consul Enterprise Automated Upgrades"
|
|
sidebar_current: "docs-enterprise-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.
|
|
---
|
|
|
|
# Consul Enterprise Automated Upgrades
|
|
|
|
[Consul Enterprise](https://www.hashicorp.com/consul.html) supports an [upgrade
|
|
pattern](https://learn.hashicorp.com/consul/day-2-operations/autopilot#upgrade-migrations)
|
|
that allows operators to deploy a complete cluster of new servers and then just wait
|
|
for the upgrade to complete. As the new servers join the cluster, server
|
|
introduction logic checks the version of each Consul server. If the version is
|
|
higher than the version on the current set of voters, it will avoid promoting
|
|
the new servers to voters until the number of new servers matches the number of
|
|
existing servers at the previous version. Once the numbers match, Autopilot will
|
|
begin to promote new servers and demote old ones.
|