Skip to content
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

Jump to bottom

[enterprise-4.16] OSSM-6086: Formatting issue in federation gateway parameters table #75546

Merged
merged 1 commit into from
May 6, 2024
Merged

[enterprise-4.16] OSSM-6086: Formatting issue in federation gateway parameters table #75546

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
22 changes: 11 additions & 11 deletions modules/ossm-federation-config-smcp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,15 +200,15 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalEgress:
<egressName>:
<egress_name>:
|Define an additional egress gateway for _each_ mesh peer in the federation.
|
|

|spec:
gateways:
additionalEgress:
<egressName>:
<egress_name>:
enabled:
|This parameter enables or disables the federation egress.
|`true`/`false`
Expand All @@ -217,7 +217,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalEgress:
<egressName>:
<egress_name>:
requestedNetworkView:
|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`.
Expand All @@ -226,7 +226,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalEgress:
<egressName>:
<egress_name>:
service:
metadata:
labels:
Expand All @@ -238,7 +238,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalEgress:
<egressName>:
<egress_name>:
service:
ports:
|Used to specify the `port:` and `name:` used for TLS and service discovery. Federation traffic consists of raw encrypted TCP for service traffic.
Expand All @@ -255,7 +255,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalIgress:
<ingressName>:
<ingress_name>:
enabled:
|This parameter enables or disables the federation ingress.
|`true`/`false`
Expand All @@ -265,7 +265,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalIngress:
<ingressName>:
<ingress_name>:
service:
type:
|The ingress gateway service must be exposed through a load balancer that operates at Layer 4 of the OSI model and is publicly available.
Expand All @@ -275,7 +275,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalIngress:
<ingressName>:
<ingress_name>:
service:
type:
|If the cluster does not support `LoadBalancer` services, the ingress gateway service can be exposed through a `NodePort` service.
Expand All @@ -285,7 +285,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalIngress:
<ingressName>:
<ingress_name>:
service:
metadata:
labels:
Expand All @@ -297,7 +297,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalIngress:
<ingressName>:
<ingress_name>:
service:
ports:
|Used to specify the `port:` and `name:` used for TLS and service discovery. Federation traffic consists of raw encrypted TCP for service traffic. Federation traffic consists of HTTPS for discovery.
Expand All @@ -307,7 +307,7 @@ To avoid naming conflicts between meshes, you must create separate egress and in
|spec:
gateways:
additionalIngress:
<ingressName>:
<ingress_name>:
service:
ports:
nodePort:
Expand Down