Prompt
Do I need Kubernetes for service discovery and load balancing?
Latest observation
Nov 5, 2026
OpenAI APIWeb search: off
No — you do not need Kubernetes just for service discovery and load balancing.
Common alternatives
- DNS-based discovery
- Services register in DNS, clients resolve names.
- Very common in cloud and microservices setups.
- Consul / etcd / ZooKeeper
- Dedicated service discovery systems.
- Support health checks, registration, and sometimes key-value config.
- Cloud load balancers
- AWS ALB/NLB, GCP Load Balancer, Azure Load Balancer can handle traffic distribution.
- Service mesh
- Istio, Linkerd, Consul Connect can provide discovery, traffic management, and retries.
- Application-level discovery
- The app queries a registry or uses static endpoints.
What Kubernetes gives you
Kubernetes includes built-in:
- Service discovery via Services and DNS
- Load balancing across Pods
- Health-based routing
- Scaling and orchestration
So Kubernetes can simplify these things, but it’s not required.
When Kubernetes makes sense
Use Kubernetes if you also want:
- container orchestration
- autoscaling
- rolling deployments
- self-healing
- multi-service management
When you may not need it
If you only need:
- simple service discovery
- basic load balancing
- a small number of services
then a lighter solution may be better.
If you want, I can also compare Kubernetes vs Consul vs cloud load balancers for your specific setup.