Load Balancing

​

Direct Load Balancer

​

Overview

• A direct load balancer is created in each location where the workload is running
• Each location obtains a public address configured as a Geo DNS target, using standard latency-based routing for traffic distribution across locations
• Domains do not need to be registered — traffic is routed directly to the workload through the load balancer
• The workload’s DNS record can be configured as a CNAME target for any source domains you wish to accept traffic for
• Users are responsible for configuring TLS certificates on the workload if required

​

Configuration

​

direct

​

ports

​

Static IP Addresses

​

Example Configuration

kind: workload
name: example-workload
spec:
  loadBalancer:
    direct:
      enabled: true
      ports:
        - externalPort: 80
          protocol: TCP
          scheme: http
          containerPort:
            port: 8080
        - externalPort: 443
          protocol: TCP
          scheme: https
          containerPort:
            port: 8443
        - externalPort: 9000
          protocol: UDP
          containerPort:
            port: 9000

{
  "kind": "workload",
  "name": "example-workload",
  "spec": {
    "loadBalancer": {
      "direct": {
        "enabled": true,
        "ports": [
          {
            "externalPort": 80,
            "protocol": "TCP",
            "scheme": "http",
            "containerPort": {
              "port": 8080
            }
          },
          {
            "externalPort": 443,
            "protocol": "TCP",
            "scheme": "https",
            "containerPort": {
              "port": 8443
            }
          },
          {
            "externalPort": 9000,
            "protocol": "UDP",
            "containerPort": {
              "port": 9000
            }
          }
        ]
      }
    }
  }
}

​

Geo Location Headers

​

Configuration

​

Usage Guidelines

1. Enabling the Feature: Set geoLocation.enabled to true to activate the Geo Location Headers feature.
2. Header Configuration: When enabled, you must specify at least one header (ASN, city, country, or region).
3. Unique Headers: The values for ASN, city, country, and region headers must be unique. You cannot use the same header name for different types of information.
4. Existing Headers: If enabled, this feature will replace any existing headers with the same names in incoming requests.

​

Notes

• Enabling this feature may have performance implications, as it requires additional processing for each incoming request.
• Enabling this feature has no effect if the workload does not expose an http port.
• Ensure that you comply with all relevant data protection and privacy regulations when using geographic information.
• The accuracy of geographic information may vary and should not be relied upon for critical decision-making without verification.
• Workloads receive the latest ip to geo database on startup.

​

Example Configuration

• X-GeoIP-ASN: Containing the Autonomous System Number
• X-GeoIP-City: Containing the city name
• X-GeoIP-Country: Containing the country name
• X-GeoIP-Region: Containing the region name

loadBalancer:
  geoLocation:
    enabled: true
    headers:
      asn: X-GeoIP-ASN
      city: X-GeoIP-City
      country: X-GeoIP-Country
      region: X-GeoIP-Region

​

Geo Location Filtering