Chapter 65: Kubernetes Domain Names and HTTPS: Ingress, DNS, ExternalDNS, cert-manager and Gateway API
Users domain name type kartat, IP nahi. Ingress ne ek entry point banvaycha, DNS record ne naav jodaycha, ExternalDNS ne te automatic karaycha aani cert-manager ne HTTPS free madhe ghyaycha. Shevti Gateway API, Ingress cha navin replacement, pan haatane chalvun bagha.
What you will learn in this chapter
- Expose many Services behind one entry point with Ingress
- Route traffic by host name and URL path
- Create DNS records by hand and understand A, CNAME, alias and TTL
- Let ExternalDNS create Route 53 records from Ingress objects
- Get free, auto-renewing HTTPS certificates with cert-manager and Let's Encrypt
- Move to Gateway API with Gateway and HTTPRoute objects
- Put it all together for shop.example.com on AWS
Concepts in this chapter
- 65.1Ingress and Ingress controllers: one entry point for many Services
- 65.2Host and path routing with DNS records: A, CNAME, alias and TTL
- 65.3ExternalDNS with Route 53: DNS records that follow your Ingress
- 65.4cert-manager and Let's Encrypt: free HTTPS that renews itself
- 65.5Gateway API: Gateway, HTTPRoute, HTTPS and traffic splitting
- 65.6End-to-end on AWS: shop.example.com with ALB, ACM, Route 53 and ExternalDNS
The chapter recap is at the end of the last concept page.