|
|
@ -25,6 +25,7 @@ For upgrades we strive to ensure backwards compatibility. To support this,
|
|
|
|
nodes gossip their protocol version and builds. This enables clients and
|
|
|
|
nodes gossip their protocol version and builds. This enables clients and
|
|
|
|
servers to intelligently enable new features when available, or to gracefully
|
|
|
|
servers to intelligently enable new features when available, or to gracefully
|
|
|
|
fallback to a backward compatible mode of operation otherwise.
|
|
|
|
fallback to a backward compatible mode of operation otherwise.
|
|
|
|
|
|
|
|
Visit the [General Upgrade Process](https://www.consul.io/docs/upgrading/instructions/general-process) for a detailed upgrade guide.
|
|
|
|
|
|
|
|
|
|
|
|
For most upgrades, the process is simple. Assuming the current version of
|
|
|
|
For most upgrades, the process is simple. Assuming the current version of
|
|
|
|
Consul is A, and version B is released.
|
|
|
|
Consul is A, and version B is released.
|
|
|
|