mTLS and workload identity
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
explain how services prove identity to each other.
Planned topics
- Each workload gets a short-lived certificate tied to its identity (not an IP).
- mTLS encrypts and authenticates both sides.
- Rotation is automatic; expiry failures are a classic outage cause.
- Authorization rules use identity: only checkout may call payments.
Draft outline details
Demonstration
a policy outline: strict mTLS in namespace shop; allow rule from identity checkout to payments on POST /charge; deny by default.
Check your understanding
Why identity not IP?
Show answer
Pods move and IPs are reused.
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.