Platform-native discovery
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
see how Kubernetes handles discovery (detail in MID-057).
Planned topics
- A Kubernetes Service gives a stable virtual IP and DNS name (
inventory.shop.svc) in front of changing Pods. - Only Pods that pass their readiness probe receive traffic.
- Rolling deployments add new Pods and remove old ones while keeping the name stable.
- Registries such as Eureka are mostly unnecessary on such a platform.
- A service mesh (SRB-009) can add smarter balancing and retries outside the application.
Draft outline details
Demonstration
diagram: orders Pod → Service inventory → Pods A, B, C (C failing readiness and excluded).
Check your understanding
Which mechanism keeps unhealthy Pods out of rotation?
Show answer
Readiness probes.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.