Path-Based Routing with HTTPProxy

​

Overview

1. Defines an exact path match for a specific route (e.g., /login)
2. Adds a catch-all prefix rule for all other traffic
3. Applies both rules in a single HTTPProxy resource

​

Prerequisites

• datumctl installed and authenticated
• A valid Project

datumctl get httpproxy

​

Configuration Steps

​

Step 1: Set Variables

PROJECT="my-project"
NAMESPACE="default"
PROXY_NAME="my-proxy"
HOSTNAME="app.example.com"

$PROJECT    = "my-project"
$NAMESPACE  = "default"
$PROXY_NAME = "my-proxy"
$HOSTNAME   = "app.example.com"

​

Step 2: Apply Path Routing Configuration

cat <<EOF | datumctl apply --project $PROJECT --namespace $NAMESPACE -f -
apiVersion: networking.datumapis.com/v1alpha
kind: HTTPProxy
metadata:
  name: $PROXY_NAME
spec:
  hostnames:
  - $HOSTNAME
  rules:
  - name: login-exact
    matches:
    - path:
        type: Exact
        value: /login
    backends:
    - endpoint: https://auth-origin.example

  - name: catch-all
    matches:
    - path:
        type: PathPrefix
        value: /
    backends:
    - endpoint: https://web-origin.example
EOF

@"
apiVersion: networking.datumapis.com/v1alpha
kind: HTTPProxy
metadata:
  name: $PROXY_NAME
spec:
  hostnames:
  - $HOSTNAME
  rules:
  - name: login-exact
    matches:
    - path:
        type: Exact
        value: /login
    backends:
    - endpoint: https://auth-origin.example

  - name: catch-all
    matches:
    - path:
        type: PathPrefix
        value: /
    backends:
    - endpoint: https://web-origin.example
"@ | datumctl apply --project $PROJECT --namespace $NAMESPACE -f -

​

Verification

​

Exact Path Match

curl -v https://app.example.com/login

​

Negative Test — Exact Is Truly Exact

curl -v https://app.example.com/login/reset

​

Catch-All

curl -v https://app.example.com/

​

Cleanup

datumctl delete httpproxy $PROXY_NAME \
  --project $PROJECT --namespace $NAMESPACE --ignore-not-found

datumctl delete httpproxy $PROXY_NAME `
  --project $PROJECT --namespace $NAMESPACE --ignore-not-found

​

Best Practices

• Always include a PathPrefix / catch-all so no requests are dropped unexpectedly
• Place more-specific rules (e.g., Exact, longer prefixes) before less-specific ones
• Use distinct, descriptive rule name values — they appear in logs and aid debugging
• Test both the matching path and a near-miss (e.g., /login/reset) to confirm exact boundaries

​

Summary

• Path-based routing is configured using a HTTPProxy resource at networking.datumapis.com/v1alpha
• Use type: Exact for single endpoints like /login
• Use type: PathPrefix with value / as a catch-all for all remaining traffic
• Rule order matters — place specific matches before the catch-all