You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: control-plane/roles/isolated-clusters/README.md
+26-4Lines changed: 26 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,13 +8,26 @@ It contains the services:
8
8
- Registry
9
9
- DNS
10
10
- NTP
11
+
- Ingress Controller (nginx-ingress)
12
+
- Envoy Gateway (optional, alternative to nginx-ingress)
11
13
12
14
A cert-manager is expected to be deployed by the user beforehand.
13
15
16
+
## Ingress vs Envoy Gateway
17
+
18
+
This role supports two options for exposing services:
19
+
20
+
1.**nginx-ingress** (default, enabled by default): Traditional Ingress controller for HTTP/HTTPS traffic and TCP/UDP proxying
21
+
2.**Envoy Gateway** (optional): Modern Gateway API implementation supporting HTTP/HTTPS, TCP, and UDP protocols
22
+
23
+
You can enable/disable each option independently using the `isolated_clusters_ingress_controller_enabled` and `isolated_clusters_envoy_gateway_enabled` variables. Both can be enabled simultaneously if needed.
24
+
14
25
## Variables
15
26
16
27
The `control-plane-defaults` folder contains defaults that are used by multiple roles in the control-plane directory. You can look up all the default values [here](control-plane-defaults/main.yaml).
17
28
29
+
**Note:** Variables marked with `yes*` are conditionally mandatory - they are only required when the corresponding feature is enabled.
| isolated_clusters_ingress_controller_namespace || The namespace where the ingress controller should be deployed to. |
28
-
| isolated_clusters_ingress_controller_chart_version | yes | The version of the ingress controller chart. |
42
+
| isolated_clusters_ingress_controller_chart_version | yes*| The version of the ingress controller chart (required if ingress enabled).|
29
43
| isolated_clusters_ingress_controller_chroot || Indicates if the image should have a changed root. |
30
-
| isolated_clusters_ingress_controller_load_balancer_ip | yes | The load balancer source ip of the ingress controller. |
31
-
| isolated_clusters_ingress_controller_load_balancer_source_ranges | yes | The load balancer source ranges of the ingress controller. |
44
+
| isolated_clusters_ingress_controller_load_balancer_ip | yes*| The load balancer source ip of the ingress controller (required if ingress enabled). |
45
+
| isolated_clusters_ingress_controller_load_balancer_source_ranges | yes*| The load balancer source ranges of the ingress controller (required if ingress enabled). |
0 commit comments