TLS Termination and Securing Ingress with HTTPS
Serve traffic over HTTPS by configuring TLS on your Ingress, storing certificates as Secrets, and automating issuance with cert-manager.
Why TLS at the Ingress
Terminating TLS at the Ingress lets one place handle HTTPS for many backend services, so internal apps can stay plain HTTP while users get encryption.
Certificates Live in Secrets
An Ingress references a TLS certificate stored in a Kubernetes Secret of type kubernetes.io/tls, holding a tls.crt and tls.key.
kubectl create secret tls my-tls \
--cert=tls.crt --key=tls.keyAll lessons in this course
- Kubernetes Ingress & Routing
- Implementing Network Policies
- Service Discovery & DNS in K8s
- TLS Termination and Securing Ingress with HTTPS