Fluid Requirements¶
Compute Requirements
x86_64
at least an AMD EPYC 7443P or Intel Xeon E-2388G
Minimum 16GB of RAM, 64GB Recommended
Network Requirements
Port + Protocol |
Name |
Traffic Flow |
Endpoint |
Purpose |
|---|---|---|---|---|
80 TCP |
HTTP |
Outbound |
*.fluidhq.io |
Used for iPXE to download the Fluid install script |
443 TCP |
HTTPS |
Outbound |
*.fluidhq.io |
Used to download Fluid OS, Software and tools |
3021-3024 & 3080 TCP |
Fluid Support access (Teleport) |
Outbound |
*.fluidhq.io |
Used to establish secured tunnels for Fluid engineering support use during troubleshooting |
4242 UDP |
Fluid Networking (Nebula) |
Outbound |
*.fluidhq.io AND the lighthouse IP address shown in the Fluid portal for each cluster |
Used to establish secured tunnels between Fluid nodes for data plane traffic and to the Fluid cloud service for VNC/Kube for control plane traffic |
*.fluidhq.io IP addresses as at date of publication
103.249.124.0/22
45.76.115.247/32
139.180.168.183/32
149.28.164.171/32
45.76.113.124/32
45.76.121.153/32
139.180.170.220/32
113.29.244.30/32
Addressing Requirements
Fluid requires nodes to receive a DHCP address on boot that can also provide PXE boot options (option 82, option 128) to nodes when they boot, and persistent (top priority) to PXE on boot for Fluid’s Immutable support.
Nodes will automatically establish networking with each other, so L2 or L3 adjacency is not required between Fluid nodes. A subnet(s) is required to advertise Fluid services outbound which is advertised over a BGP peer. These subnets can be public or private, provided the wider network can handle them appropriately. See BGP Configuration for more information about peering.