OSSM 3
OpenShift Service Mesh 3
OSSM 3 ambient mode is enabled on both workload spokes. The platform is ready; the remaining work is application namespace opt-in and validation.
Live state
Recorded platform status
| Cluster | Operators | Control plane | Workload state |
|---|---|---|---|
spoke-dc | servicemeshoperator3.v3.3.2, kiali-operator.v2.22.2 | Istio/default, IstioCNI/default, and ZTunnel/default healthy at v1.28.5 | No application namespace has opted into ambient yet. |
spoke-dr | servicemeshoperator3.v3.3.2, kiali-operator.v2.22.2 | Istio/default, IstioCNI/default, and ZTunnel/default healthy at v1.28.5 | No application namespace has opted into ambient yet. |
Onboarding
Application checklist
- Select workload: define which app should enter the mesh and which spoke owns the first deployment.
- Define namespace labels: use
istio.io/dataplane-mode=ambientfor namespaces that should join ambient mode. - Add routing: create Gateway and VirtualService resources if external or cross-service mesh routing is required.
- Validate telemetry: check Kiali graph, service health, and request paths after traffic is generated.
- Record DR behavior: document whether spoke-dr is passive platform standby or active app standby for the workload.
Caveats
Known integration notes
- No Bookinfo, metrics-demo, otel-demo, liberty-canary, or demo-orders namespaces exist on either spoke.
demo-ordershas been wiped and should not be used unless intentionally recreated.spoke-drhas an OpenShift AI ServiceMesh capability marked missing because it expects the old OSSM v2 operator. OSSM 3 itself is not blocked.