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: deployments/liqo/README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,7 +128,7 @@
128
128
| nameOverride | string |`""`| Override the standard name used by Helm and associated to Kubernetes/Liqo resources. |
129
129
| networking.clientResources | list |`[{"apiVersion":"networking.liqo.io/v1alpha1","resource":"wggatewayclients"}]`| Set the list of resources that implement the GatewayClient |
130
130
| networking.enabled | bool |`true`| Use the default Liqo networking module. |
131
-
| networking.gatewayTemplates | object |`{"container":{"gateway":{"image":{"name":"ghcr.io/liqotech/gateway","version":""}},"geneve":{"image":{"name":"ghcr.io/liqotech/gateway/geneve","version":""}},"wireguard":{"image":{"name":"ghcr.io/liqotech/gateway/wireguard","version":""}}},"ping":{"interval":"2s","lossThreshold":5,"updateStatusInterval":"10s"},"replicas":1,"server":{"service":{"allocateLoadBalancerNodePorts":"","annotations":{"service.beta.kubernetes.io/aws-load-balancer-type":"nlb"}}}}`| Set the options for the default gateway (server/client) templates. The default templates use a WireGuard implementation to connect the gateway of the clusters. These options are used to configure only the default templates and should not be considered if a custom template is used. |
131
+
| networking.gatewayTemplates | object |`{"container":{"gateway":{"image":{"name":"ghcr.io/liqotech/gateway","version":""}},"geneve":{"image":{"name":"ghcr.io/liqotech/gateway/geneve","version":""}},"wireguard":{"image":{"name":"ghcr.io/liqotech/gateway/wireguard","version":""}}},"ping":{"interval":"2s","lossThreshold":5,"updateStatusInterval":"10s"},"replicas":1,"server":{"service":{"allocateLoadBalancerNodePorts":"","annotations":{"service.beta.kubernetes.io/aws-load-balancer-type":"nlb"}}},"wireguard":{"implementation":"kernel"}}`| Set the options for the default gateway (server/client) templates. The default templates use a WireGuard implementation to connect the gateway of the clusters. These options are used to configure only the default templates and should not be considered if a custom template is used. |
132
132
| networking.gatewayTemplates.container.gateway.image.name | string |`"ghcr.io/liqotech/gateway"`| Image repository for the gateway container. |
133
133
| networking.gatewayTemplates.container.gateway.image.version | string |`""`| Custom version for the gateway image. If not specified, the global tag is used. |
134
134
| networking.gatewayTemplates.container.geneve.image.name | string |`"ghcr.io/liqotech/gateway/geneve"`| Image repository for the geneve container. |
@@ -144,6 +144,7 @@
144
144
| networking.gatewayTemplates.server.service | object |`{"allocateLoadBalancerNodePorts":"","annotations":{"service.beta.kubernetes.io/aws-load-balancer-type":"nlb"}}`| Set the options to configure the server service |
145
145
| networking.gatewayTemplates.server.service.allocateLoadBalancerNodePorts | string |`""`| Set to "false" if you expose the gateway service as LoadBalancer and you do not want to create also a NodePort associated to it (Note: this setting is useful only on cloud providers that support this feature). |
146
146
| networking.gatewayTemplates.server.service.annotations | object |`{"service.beta.kubernetes.io/aws-load-balancer-type":"nlb"}`| Annotations for the server service. |
147
+
| networking.gatewayTemplates.wireguard.implementation | string |`"kernel"`| Set the implementation used for the WireGuard connection. Possible values are "kernel" and "userspace". |
| networking.iptables.mode | string |`"nf_tables"`| Select the iptables mode to use. Possible values are "legacy" and "nf_tables". |
149
150
| networking.mtu | int |`1340`| Set the MTU for the interfaces managed by liqo: vxlan, tunnel and veth interfaces. The value is used by the gateway and route operators. The default value is configured to ensure correct behavior regardless of the combination of the underlying environments (e.g., cloud providers). This guarantees improved compatibility at the cost of possible limited performance drops. |
0 commit comments