How does Kubernetes manage service discovery in a microservices-based system?

Short answer: In Kubernetes, service discovery is managed through the Kubernetes DNS system.

Explain a bit more

Each service is given a DNS name that resolves to its pods (or group of pods), allowing services to find and communicate with each other. Kubernetes Services: A Kubernetes Service is an abstraction layer over a set of Pods. Services provide a stable IP address and DNS name, even though the Pods may be dynamically created or destroyed. For example, a service named order-service in the default namespace would be reachable as order-service.default.svc.cluster.local. Kubernetes DNS: Kubernetes automatically configures DNS for services in a cluster, so services can resolve the name of another service (e.g., order-service) to the appropriate IP address. Service Types: Kubernetes supports different service types like ClusterIP, NodePort, and LoadBalancer, each serving different use cases for internal or external service discovery.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.