Skip to content

Commit 17218b6

Browse files
cnvergencecnvergence
committed
review update
Signed-off-by: Karol Szwaj <[email protected]>
1 parent 4fc5337 commit 17218b6

File tree

2 files changed

+24
-24
lines changed

2 files changed

+24
-24
lines changed

‎site/content/en/latest/tasks/operations/gateway-namespace-mode.md‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ For status updates or to provide feedback, please follow our [GitHub issues](htt
1010

1111
{{% /alert %}}
1212

13-
# Overview
13+
## Overview
1414

1515
In standard deployment mode, Envoy Gateway creates all data plane resources in the controller namespace (typically `envoy-gateway-system`).
1616

@@ -32,11 +32,11 @@ Currently it is not supported to run Gateway Namespace Mode with Merged Gateways
3232

3333
{{% /alert %}}
3434

35-
# Configuration
35+
## Configuration
3636

3737
To enable Gateway Namespace Mode, configure the `provider.kubernetes.deploy.type` field in your Envoy Gateway ConfigMap:
3838

39-
```bash
39+
```yaml
4040
apiVersion: gateway.envoyproxy.io/v1alpha1
4141
kind: EnvoyGateway
4242
metadata:
@@ -52,18 +52,18 @@ spec:
5252
5353
To install Envoy Gateway with Gateway Namespace Mode using Helm:
5454
55-
```bash
55+
```shell
5656
helm install \
5757
--set config.envoyGateway.provider.kubernetes.deploy.type=GatewayNamespace \
5858
eg oci://docker.io/envoyproxy/gateway-helm \
59-
--version latest -n envoy-gateway-system --create-namespace
59+
--version {{< helm-version >}} -n envoy-gateway-system --create-namespace
6060
```
6161

62-
## RBAC configuration
62+
### RBAC configuration
6363

6464
When using Gateway Namespace Mode, Envoy Gateway needs additional RBAC permissions to create and manage resources across different namespaces. The following RBAC resources are automatically created when installing Envoy Gateway Helm Chart with Gateway Namespace Mode enabled.
6565

66-
```bash
66+
```yaml
6767
apiVersion: rbac.authorization.k8s.io/v1
6868
kind: ClusterRole
6969
metadata:
@@ -100,23 +100,23 @@ Envoy Gateway also supports configuration to you only watch resources in the spe
100100
`EnvoyGateway.provider.kubernetes.watch.namespaces` or `EnvoyGateway.provider.kubernetes.watch.namespaceSelector`.
101101
In this case, when you specify this configuration with Gateway Namespace Mode,Envoy Gateway will only watch for Gateway API resources in the specified namespaces and create needed Roles for infrastructure management in the specified namespaces.
102102

103-
# Testing
103+
## Testing
104104

105105
The following example demonstrates deploying two Gateways in different namespaces `team-a` and `team-b`.
106106

107-
## Create test namespaces
107+
### Create test namespaces
108108

109109
```shell
110110
kubectl create namespace team-a
111111
kubectl create namespace team-b
112112
```
113113

114-
## Deploy Gateway Namespace Mode Example
114+
### Deploy Gateway Namespace Mode Example
115115

116116
Deploy resources on your cluster from the example, it will create two sets of backend deployments, Gateways and their respective HTTPRoutes in the previously created namespaces `team-a` and `team-b`.
117117

118118
```shell
119-
kubectl apply -f https://raw.githubusercontent.com/envoyproxy/gateway/latest/examples/kubernetes/gateway-namespace-mode.yaml
119+
kubectl apply -f https://raw.githubusercontent.com/envoyproxy/gateway/{{< yaml-version >}}/examples/kubernetes/gateway-namespace-mode.yaml
120120
```
121121

122122
Verify that Gateways are deployed and programmed
@@ -185,7 +185,7 @@ envoy-team-b-gateway-b-0ac91f5a LoadBalancer 10.96.144.13 172.18.0.201 8
185185
team-b-backend ClusterIP 10.96.26.162 <none> 3000/TCP 3m43s
186186
```
187187

188-
## Testing the Configuration
188+
### Testing the Configuration
189189

190190
Fetch external IPs of the services:
191191

‎site/content/en/v1.4/tasks/operations/gateway-namespace-mode.md‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ For status updates or to provide feedback, please follow our [GitHub issues](htt
1010

1111
{{% /alert %}}
1212

13-
# Overview
13+
## Overview
1414

1515
In standard deployment mode, Envoy Gateway creates all data plane resources in the controller namespace (typically `envoy-gateway-system`).
1616

@@ -32,11 +32,11 @@ Currently it is not supported to run Gateway Namespace Mode with Merged Gateways
3232

3333
{{% /alert %}}
3434

35-
# Configuration
35+
## Configuration
3636

3737
To enable Gateway Namespace Mode, configure the `provider.kubernetes.deploy.type` field in your Envoy Gateway ConfigMap:
3838

39-
```bash
39+
```yaml
4040
apiVersion: gateway.envoyproxy.io/v1alpha1
4141
kind: EnvoyGateway
4242
metadata:
@@ -52,18 +52,18 @@ spec:
5252
5353
To install Envoy Gateway with Gateway Namespace Mode using Helm:
5454
55-
```bash
55+
```shell
5656
helm install \
5757
--set config.envoyGateway.provider.kubernetes.deploy.type=GatewayNamespace \
5858
eg oci://docker.io/envoyproxy/gateway-helm \
59-
--version latest -n envoy-gateway-system --create-namespace
59+
--version {{< helm-version >}} -n envoy-gateway-system --create-namespace
6060
```
6161

62-
## RBAC configuration
62+
### RBAC configuration
6363

6464
When using Gateway Namespace Mode, Envoy Gateway needs additional RBAC permissions to create and manage resources across different namespaces. The following RBAC resources are automatically created when installing Envoy Gateway Helm Chart with Gateway Namespace Mode enabled.
6565

66-
```bash
66+
```yaml
6767
apiVersion: rbac.authorization.k8s.io/v1
6868
kind: ClusterRole
6969
metadata:
@@ -100,23 +100,23 @@ Envoy Gateway also supports configuration to you only watch resources in the spe
100100
`EnvoyGateway.provider.kubernetes.watch.namespaces` or `EnvoyGateway.provider.kubernetes.watch.namespaceSelector`.
101101
In this case, when you specify this configuration with Gateway Namespace Mode,Envoy Gateway will only watch for Gateway API resources in the specified namespaces and create needed Roles for infrastructure management in the specified namespaces.
102102

103-
# Testing
103+
## Testing
104104

105105
The following example demonstrates deploying two Gateways in different namespaces `team-a` and `team-b`.
106106

107-
## Create test namespaces
107+
### Create test namespaces
108108

109109
```shell
110110
kubectl create namespace team-a
111111
kubectl create namespace team-b
112112
```
113113

114-
## Deploy Gateway Namespace Mode Example
114+
### Deploy Gateway Namespace Mode Example
115115

116116
Deploy resources on your cluster from the example, it will create two sets of backend deployments, Gateways and their respective HTTPRoutes in the previously created namespaces `team-a` and `team-b`.
117117

118118
```shell
119-
kubectl apply -f https://raw.githubusercontent.com/envoyproxy/gateway/latest/examples/kubernetes/gateway-namespace-mode.yaml
119+
kubectl apply -f https://raw.githubusercontent.com/envoyproxy/gateway/{{< yaml-version >}}/examples/kubernetes/gateway-namespace-mode.yaml
120120
```
121121

122122
Verify that Gateways are deployed and programmed
@@ -185,7 +185,7 @@ envoy-team-b-gateway-b-0ac91f5a LoadBalancer 10.96.144.13 172.18.0.201 8
185185
team-b-backend ClusterIP 10.96.26.162 <none> 3000/TCP 3m43s
186186
```
187187

188-
## Testing the Configuration
188+
### Testing the Configuration
189189

190190
Fetch external IPs of the services:
191191

0 commit comments

Comments
 (0)