Make compat version support more explicit (#15997)

* Make compat version support more explicit

Signed-off-by: Benjamin Leggett <benjamin.leggett@solo.io>

* Update content/en/docs/setup/additional-setup/compatibility-versions/index.md

Co-authored-by: Craig Box <craig.box@gmail.com>

* Update content/en/docs/setup/additional-setup/compatibility-versions/index.md

---------

Signed-off-by: Benjamin Leggett <benjamin.leggett@solo.io>
Co-authored-by: Craig Box <craig.box@gmail.com>
This commit is contained in:
Ben Leggett 2024-11-26 11:01:49 -05:00 committed by GitHub
parent ee23ed004f
commit 9a7d53fd3c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions

View File

@ -40,9 +40,9 @@ $ helm install ... --set compatibilityVersion={{< istio_previous_version >}}
## When should I use compatibility versions?
Compatibility versions are recommended to be used only when an incompatibility is found, rather than as the default.
Each compatibility version will only persist for a few releases, so eventually you will need to migrate to the new behavior.
Currently, each compatibility version is intended to remain for at least two versions, though this is subject to change.
Compatibility versions should be used only when an incompatibility between releases exists, as a temporary measure. You should plan to migrate to the new behavior as soon as practical.
Compatibility versions for a release will be removed, and will no longer be supported, when the release they refer to reaches end-of-life. Refer to the [current Istio release support status chart](/docs/releases/supported-releases/#support-status-of-istio-releases) for the status of specific releases.
To help detect if a compatibility version should be used, `istioctl x precheck` can be used with the `--from-version` flag.
For instance, if you are upgrading from version {{< istio_previous_version >}}: