Containers: egress IPs and internal addresses

Egress IPs (for the IP allow list of a database, payment provider or partner API): GET /cloud/containers/{id}/egress-ips (gyro container egress-ips <id>, Terraform data "gyro_container_environment" → egress_ips). Add all listed addresses. A dedicated environment leaves the internet from its own node IPs, plus the shared pool node while an update rolls out (about a minute); a serverless environment from the shared pool nodes. The list changes when the nodes change (plan change, node replacement, pool scaling); the owner is notified (alert event egress). IPv4 only; outbound TCP 25 is closed.

Namespace and internal addressing: GET /cloud/containers/{id} returns the Kubernetes namespace (e.g. t-canli-12345) and cluster_dns. Services of the same environment reach each other at <service>.<namespace>.svc.cluster.local:80 or simply <service>:80 (port 80 is forwarded to the container port; only services with a port). The service detail has internal.address. Other environments cannot reach these addresses.