-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
At the moment, the upgrade page makes only a mention at the beginning to 2.2, but the sections below are very specific to 2.0 and 2.1. The procedure should be the same between 2.x releases, so we should make these generic to reflect that.
We have a generic operator upgrade section, but then go version specific for the control plane and data plane. Perhaps consider sections like "Upgrade the operators", "Upgrade the control plane(s)", "Upgrade the dataplane(s)".
These sections should cover questions, such as:
- Can multiple versions of the control plane be deployed in the same cluster?
- Can the control plane version differ from the data plane version? When is this state supported?
For the 2.0 and 2.1 sections, some content also looks like it should have been in release notes rather than the upgrade page (e.g. "Changes from prior release"). Perhaps these and any other version specific information can be removed.
- is blocked by
-
OSSM-2648 Break Upgrade workflow up to leverage mod doc approach
-
- Closed
-
- links to