Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The upgrade paths table in our documentation is massive and often incorrect. There are no new tests or findings for these paths in each release, so all the table says is to upgrade step by step to each minor version (3.4.x to 3.5.x to 3.6.x, etc). Additionally, this table is split by topology, but there is absolutely no difference in paths for each topology.
This table was added around 3.1 to cover the cover the websocket protocol changes between patches. However, this special case is already covered in https://docs.konghq.com/gateway/latest/upgrade/#upgrades-from-3100-or-3111.
I believe that simply adding examples to the list of supported guaranteed paths will serve the same purpose that the table once did, but in a much clearer way.
https://konghq.atlassian.net/browse/DOCU-3998
https://konghq.atlassian.net/browse/DOCU-4157
Testing instructions
Preview link: https://deploy-preview-8188--kongdocs.netlify.app/gateway/latest/upgrade/#preparation-choose-an-upgrade-path
Checklist