In-cluster egress communication
If you are using a firewall or any other method to filter egress communication, please ensure that the following addresses are allowed for outbound communication. This is necessary to operate the in-cluster components.
All communication should be routed through or directed to port 443 for secure HTTPS communication.
Service | IPv4 | IPv6 |
---|---|---|
ARMO Platform | 16.170.46.131 13.50.180.111 16.171.184.118 | N/A |
Grype (vulnerabilities scanning) | 172.67.71.75 104.26.0.250 104.26.1.250 | 2606:4700:20::681a:1fa 2606:4700:20::ac43:474b 2606:4700:20::681a:fa |
GitHub (Policies download) | 140.82.121.4 185.199.109.133 185.199.110.133 185.199.111.133 185.199.108.133 | 2606:50c0:8003::154 2606:50c0:8000::154 2606:50c0:8001::154 2606:50c0:8002::154 |
Frontegg (identity provider) | 99.81.198.187 54.216.181.43 52.209.54.22 | N/A |
Falco Runtime (Relevancy) | 65.9.112.122 65.9.112.93 65.9.112.127 65.9.112.120 | 2600:9000:2024:9600:2:7d42:ee80:93a1 2600:9000:2024:4200:2:7d42:ee80:93a1 2600:9000:2024:1c00:2:7d42:ee80:93a1 2600:9000:2024:2a00:2:7d42:ee80:93a1 2600:9000:2024:3800:2:7d42:ee80:93a1 2600:9000:2024:9c00:2:7d42:ee80:93a1 2600:9000:2024:fc00:2:7d42:ee80:93a1 2600:9000:2024:f400:2:7d42:ee80:93a1 |
Updated 2 months ago