Skip to main content

Configure Egress Rules

Let the applications of a project call specific outside services. The platform denies outbound traffic from a project by default. Google's services, the Debian and Windows update servers and private addresses inside your network (10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16) are always allowed.

Prerequisites​

  • A Project manifest.
  • The host names or IP ranges that your applications must reach.

Steps​

  1. Add allowedEgress to spec of the Project.

    apiVersion: lowops.manifests.v1
    kind: Project
    metadata:
    name: payment-gateway
    environment: production
    organizational-unit: retail-banking
    organization: fincorp
    spec:
    region: us-central1
    allowedEgress:
    - "api.stripe.com"
    - "hooks.slack.com"
    - "smtp.sendgrid.net"
  2. Commit the manifest in a pull request and merge it.

The list applies to all applications in the project. Egress rules only add allowed destinations. They cannot block traffic that the platform allows by default.

Verify​

The platform updates the firewall rules of the Shared VPC. Applications can reach the new destinations at once. They need no restart.

If an application gets a connection timeout from an outside API, add the host name of the API to allowedEgress.

Next​