-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
With the addition of ambient mode, there will be two separate paths after the operator is installed. Some things will be common to both paths, but others will only be applicable to sidecar or ambient mode.
A potential division:
Common Sections (applies to both Sidecar and Ambient mode):
- 1 Supported Platforms and configurations
- 2 Installing OpenShift Service Mesh sections:
- 2.1 - About the operator
- 2.2 - Installing the operator
- 2.4 - Scoping the mesh
- 2.6 - Customizing the Istio configuration
- 2.7 - Istio high availability (Istiod)
- 5 OpenShift Service Mesh and cert-manager
- 9 Istioctl tool
- 10 Enabling mutual Transport Layer Security (needs review)
Sidecar mode specific sections:
- 2 Installing OpenShift Service Mesh sections:
- 2.3 - About the Istio deployment (example is for Sidecar mode)
- 2.5 - Bookinfo application (example is for sidecar mode)
- 3 Sidecar Injection
- 6 Multi-cluster topologies (maybe - upstream classes as sidecar mode)
- 7 External Control Plane topologies (maybe - upstream classes as sidecar mode)
- 8 Deploying Multiple Service Meshes in a single cluster (maybe - upstream classes as sidecar mode)
Ambient specific sections:
- 4 Istio Ambient mode
- Picks up after Installation section 2.2 has been completed.
- Covers installing the ZTunnel
- Needs addition for Waypoint installation - https://issues.redhat.com/browse/OSSM-10021
- In the "Installing OpenShift Service Mesh" page, add a heading/note to section "2.3 About Istio deployment", that indicates the example going forward is for Sidecar mode, and that there is a separate section for sidecar-less ambient mode.
- Alternatively, split the page from this point onward into a separate page "Installing for Sidecar mode" and "Installing for ambient mode".
- "Installing" could even be broken into separate categories - "Installing
- documents
-
OSSM-11146 Doc updates for OSSM 3.2
-
- In Progress
-