Domain Templates

Domain templates define reusable Gateway settings that domains can inherit, ensuring consistent configuration across your API infrastructure.

Template Properties

Property	Description	Options
Exposure Type	Network accessibility	public (internet-facing), internal (cluster-only)
Port	Listener port number	Any valid port (typically 80, 443, 8080)
TLS Policy	Certificate handling	terminate, passthrough, none
Annotations	Custom metadata	Key-value pairs for load balancer configuration

How Templates Work

┌──────────────────┐
│  Domain Template │
│  ─────────────── │
│  exposure: public│
│  port: 443       │
│  tls: terminate  │
└────────┬─────────┘
         │ inherits
    ┌────┴────┐
    ▼         ▼
┌────────┐ ┌────────┐
│Domain A│ │Domain B│
│api.com │ │app.com │
└────────┘ └────────┘

Common Template Patterns

Template Name	Use Case
Public HTTPS	Internet APIs with TLS termination
Internal HTTP	Cluster-internal services
Public Passthrough	mTLS or custom certificate handling

Benefits

• Consistency: All domains using a template share the same baseline configuration
• Efficiency: Update the template to change all associated domains
• Compliance: Enforce organizational standards through template policies

Templates reduce configuration drift and simplify domain management at scale.