DNS-Based Discovery
Your backends scale up and down. Trident follows automatically.
No restarts. No config changes. Just DNS.
The Problem
Traditional caches require static backend IP addresses. When you scale your backend pods, add new servers, or use cloud load balancers with dynamic IPs, you need to restart your cache or manually update configuration.
The Trident Solution
Trident resolves backend hostnames via DNS and automatically refreshes at configurable intervals. When pods scale up or down, Trident discovers new backends without any intervention.
Simple Configuration
Kubernetes Service
[[backends]]
name = "api-cluster"
host = "api-service.default.svc.cluster.local"
port = 80
[backends.discovery]
method = "dns"
refresh_interval = "30s"
use_all_addresses = trueTrident resolves the Kubernetes service DNS and load-balances across all pod IPs.
AWS NLB/ALB
[[backends]]
name = "aws-backend"
host = "my-nlb-123.elb.amazonaws.com"
port = 443
tls = true
[backends.discovery]
method = "dns"
refresh_interval = "60s"
prefer_ipv4 = trueAuto-discover AWS load balancer IPs as they change during scaling events.
How It Works
Trident resolves DNS and load-balances across all discovered IPs with auto-refresh
Features
Auto-Refresh
Configurable refresh intervals from 10s to 24h. DNS TTL respected.
Round-Robin
Automatic load balancing across all resolved IPs.
Per-IP Health
Individual health tracking for each resolved address. Unhealthy IPs skipped.
IPv4/IPv6
Support for both. Configure preference with prefer_ipv4 option.
Admin CLI
dns.list and dns.refresh commands for manual control and debugging.
Metrics
DNS resolution time, success rate, and IP count in Prometheus metrics.
Use Cases
Kubernetes Deployments
Point Trident at your Kubernetes service DNS. As pods scale up/down during deployments or HPA events, Trident automatically discovers new endpoints.
AWS Auto Scaling Groups
Use NLB/ALB DNS names. When EC2 instances scale or get replaced, Trident follows the DNS changes without manual intervention.
Blue-Green Deployments
Switch DNS from blue to green environment. Trident picks up new backends on the next refresh cycle.
Multi-Region Failover
Use Route53 health checks to remove failed regions from DNS. Trident automatically routes to healthy regions.
Ready for Cloud-Native Caching?
DNS-based discovery is included in all Trident plans.