- All Courses
- Kubernetes for Application Developers
- Getting Traffic In
- TLS and certificates
TLS and certificates
TLS is normally terminated at the ingress, which holds the certificate and forwards plain traffic inside the cluster.
Overview
Certificates should renew themselves
TLS is normally terminated at the ingress, which holds the certificate and forwards plain traffic inside the cluster. That keeps certificate management in one place instead of in every service.
Manual renewal is a recurring outage waiting to happen. A controller that requests and renews certificates automatically removes an entire class of calendar-driven incident.
Certificates live in secrets, so the same access control questions apply. A private key readable by every workload in the namespace is not really private.
In this lesson you will:
- Terminate TLS at the ingress
- Automate certificate issuance and renewal
- Handle certificate secrets safely
Resources
Notes are not saved yet — they clear when you leave this page.
Ingress and routing
6m
Readiness and liveness probes
3m