Network Requirements
The following table describes the Kubernetes network requirements for UCT-C to work efficiently.
|
Direction |
Type |
Protocol |
Port |
CIDR |
Purpose |
| Universal Cloud Tap - Container deployed inside Kubernetes worker node | |||||
|
Outbound |
HTTPS |
TCP |
443 |
Any IP address |
Allows UCT-C Controller to communicate with GigaVUE‑FM |
|
Inbound |
HTTPS |
TCP |
8443 (configurable) |
Any IP address |
Allows GigaVUE‑FM to communicate with UCT-C Controller. |
| Outbound | HTTPS | TCP | 5671 | Any IP address | Allows UCT-C controller to send statistics to GigaVUE‑FM through Rabbit-MQ port. |
| Outbound | HTTPS | TCP | 42042 | Any IP address | Allows UCT-C to send statistics information to UCT-Ccontroller. |
| Outbound | HTTPS | TCP | 4789 | Any IP address | VXLAN Default Port |
The following table describes the ports that should be opened on GigaVUE‑FM:
|
Direction |
Port |
Purpose |
|
Inbound |
443 |
GigaVUE‑FM REST service port. |
|
Outbound |
8443 |
Allows GigaVUE‑FM to communicate with UCT-C Controller. |
| Inbound | 5671 | Allows UCT-C to send statistics to GigaVUE‑FM through Rabbit-MQ port. |
