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: docs/raven-agent-tutorial.md
+18-1
Original file line number
Diff line number
Diff line change
@@ -197,11 +197,28 @@ NOTE: Make sure there are no node IP conflicts in the cluster.
197
197
By default, raven uses IPSec as VPN backend, we also provide [WireGuard](https://www.wireguard.com/) as an alternative. You can switch to WireGuard backend by the following steps:
198
198
199
199
- Raven requires the WireGuard kernel module to be loaded on gateway nodes in the cluster. Starting at Linux 5.6, the kernel includes WireGuard in-tree; Linux distributions with older kernels will need to install WireGuard. For most Linux distributions, this can be done using the system package manager. For more information, see [Install WireGuard](https://www.wireguard.com/install/).
200
-
- The gateway nodes will require an open UDP port in order to communicate. By default, WireGuard uses UDP port 51820.
200
+
- The gateway nodes will require an open UDP port in order to communicate. By default, we use UDP port 4500.
201
201
- Run the following commands:
202
202
203
203
```bash
204
204
cd raven
205
205
make undeploy
206
206
VPN_DRIVER=wireguard make deploy
207
207
```
208
+
209
+
## (Optional 3) Use LoadBalancer to expose cloud gateway VPN service
210
+
211
+
By default, raven use EIP/Public IP to expose cloud gateway VPN service, we also provide LoadBalancer as an alternative. You can set `exposeType: LoadBalancer` in Gateway CR to enable it.
0 commit comments