Skip to main content

Set Up Private Ingress

Create an internal-only load balancer for services in different projects. A PrivateIngress keeps traffic in the private network of your organization. A PublicIngress exposes services to the internet.

Prerequisites​

  • An Application deployed in the target project.
  • The projects that must reach the internal API.

Steps​

  1. Create the PrivateIngress manifest.

    apiVersion: lowops.manifests.v1
    kind: PrivateIngress
    metadata:
    name: internal-api-gateway
    project: payment-gateway
    environment: production
    organizational-unit: retail-banking
    organization: fincorp
    spec:
    description: "Internal L7 gateway for payment APIs"
    region: us-central1
    authorizedProjects:
    - name: order-service
    environment: production
    organizationalUnit: retail-banking
    - name: analytics-platform
    environment: production
    organizationalUnit: data-engineering

    authorizedProjects lists the projects that get network access to the ingress. Give the name, environment and organizationalUnit of each project. The schema also has a config block and an authorizationDatabase field. The engine does not apply them yet. See the PrivateIngress reference.

  2. Create an HttpRoute for each path.

    apiVersion: lowops.manifests.v1
    kind: HttpRoute
    metadata:
    name: payments-api-route
    private-ingress: internal-api-gateway # links the route to the ingress
    project: payment-gateway
    environment: production
    organizational-unit: retail-banking
    organization: fincorp
    spec:
    rules:
    - matches:
    - prefixMatch: /api/v1/payments
    action:
    destinations:
    - deploymentConfig: payment-api
    port: 8080
  3. Commit the manifests in one pull request and merge it.

Verify​

The platform creates an internal HTTPS load balancer with TLS and connects the authorized projects to it.

Next​