Networking
Required Services
meltcloud is designed to be integrated in existing enterprise networks.
To benefit from automation and flexibility, meltcloud relies on externally provided network configuration to configure the machines.
- DHCP: provides IP addresses, routes and name servers for all interfaces
- DNS: resolve the meltcloud destinations (see matrix below)
- NTP: synchronize time of machines/workers
Machines must be able to connect to the meltcloud platform and its designated Kubernetes API endpoint, as listed below:
Port Matrix
INFO
Be aware that all connections using TLS are based on X509 client certificates which cannot be intercepted by an HTTP proxy.
| Source | Destination | Destination meltcloud.io | Ports/Protocols | Reason |
|---|---|---|---|---|
| Machine | DHCP-Server | - | DHCP | To assign network config |
| Machine | DNS-Server | - | 53/tcp/udp (DNS) | To resolve endpoints below |
| Machine | NTP-Server | - | 123/udp (NTP) | To synchronize time |
| Machine | meltcloud Foundry | *.meltcloud.io (149.202.23.1315) | 443/tcp (TLS) & 80/tcp (optional, if enrolling via HTTP) | For Machine communication |
| Machine | meltcloud Package Repository | pkg.meltcloud.io (62.210.39.76) | 443/tcp (TLS) | To download packages |
| Machine | meltcloud Kubernetes API Server Endpoint | 149.202.23.132 | different port per cluster, see Console (TLS) | For Kubeadm/Kubelet to reach Kubernetes API servers |