Skip to content

Commit

Permalink
stable-2.14.0 upgrade instructions (linkerd#1660)
Browse files Browse the repository at this point in the history
* stable-2.14.0 upgrade instructions

Co-authored-by: Eliza Weisman <[email protected]>
  • Loading branch information
2 people authored and sourishkrout committed Aug 23, 2023
1 parent 7753995 commit fd1005f
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions linkerd.io/content/2-edge/tasks/upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ Read through this guide carefully. Additionally, before starting a specific
upgrade, please read through the version-specific upgrade notices below, which
may contain important information about your version.

- [Upgrade notice: stable-2.14.0](#upgrade-notice-stable-2-14-0)
- [Upgrade notice: stable-2.13.0](#upgrade-notice-stable-2-13-0)
- [Upgrade notice: stable-2.12.0](#upgrade-notice-stable-2-12-0)
- [Upgrade notice: stable-2.11.0](#upgrade-notice-stable-2-11-0)
Expand Down Expand Up @@ -229,6 +230,16 @@ version.

## Upgrade notices

### Upgrade notice: stable-2.14.0

For this release, if you're using the multicluster extension, you should re-link
your clusters after upgrading to stable-2.14.0, as explained
[above](#upgrading-the-multicluster-extension). Not doing so immediately won't
cause any downtime in cross-cluster connections, but `linkerd multicluster
check` will not succeed until the clusters are re-linked.

There are no other extra steps for upgrading to 2.14.0.

### Upgrade notice: stable-2.13.0

Please be sure to read the [Linkerd 2.13.0 release
Expand Down

0 comments on commit fd1005f

Please sign in to comment.