Skip to content

OSSM-3159 Remove routerMode: sni-dnat from federation docs #69120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 12, 2023
Merged

OSSM-3159 Remove routerMode: sni-dnat from federation docs #69120

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 0 additions & 21 deletions modules/ossm-federation-config-smcp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,6 @@ spec:
enabled: true
requestedNetworkView:
- green-network
routerMode: sni-dnat
service:
metadata:
labels:
Expand All @@ -45,7 +44,6 @@ spec:
enabled: true
requestedNetworkView:
- blue-network
routerMode: sni-dnat
service:
metadata:
labels:
Expand All @@ -58,7 +56,6 @@ spec:
additionalIngress:
ingress-green-mesh:
enabled: true
routerMode: sni-dnat
service:
type: LoadBalancer
metadata:
Expand All @@ -71,7 +68,6 @@ spec:
name: https-discovery #note HTTPS here
ingress-blue-mesh:
enabled: true
routerMode: sni-dnat
service:
type: LoadBalancer
metadata:
Expand Down Expand Up @@ -146,14 +142,6 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|Networks associated with exported services.
|Set to the value of `spec.cluster.network` in the SMCP for the mesh, otherwise use <ServiceMeshPeer-name>-network. For example, if the `ServiceMeshPeer` resource for that mesh is named `west`, then the network would be named `west-network`.
|

|spec:
gateways:
additionalEgress:
<egressName>:
routerMode:
|The router mode to be used by the gateway.
|`sni-dnat`
|

|spec:
Expand Down Expand Up @@ -194,14 +182,6 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|`true`/`false`
|`true`

|spec:
gateways:
additionalIngress:
<ingressName>:
routerMode:
|The router mode to be used by the gateway.
|`sni-dnat`
|

|spec:
gateways:
Expand Down Expand Up @@ -266,7 +246,6 @@ In the following example, the administrator is configuring the SMCP for federati
additionalIngress:
ingress-green-mesh:
enabled: true
routerMode: sni-dnat
service:
type: NodePort
metadata:
Expand Down