Services and Ingress
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
give pods a stable address and expose them.
Planned topics
- A Service gives a stable name and virtual IP and load-balances across matching ready pods.
- Types: ClusterIP (internal), NodePort, LoadBalancer (cloud load balancer).
- Ingress (or the Gateway API) routes HTTP by host and path to Services, via an ingress controller.
- Services find each other by DNS:
http://inventory:8080.
Draft outline details
Demonstration
Ingress routing /api/orders to the orders Service and /api/catalog to catalog.
Check your understanding
Why a Service instead of pod IPs?
Show answer
Pods are replaced and their IPs change; the Service name is stable.
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.