In Kubernetes, an Ingress is a way to describe how to route traffic coming into the cluster, so that (for example)
https://radarr.example.com will end up on a Radarr pod, but
https://sonarr.example.com will end up on a Sonarr pod.
There are many popular Ingress Controllers, we're going to cover two equally useful options:
Choose at least one of the above (there may be valid reasons to use both! 1), so that you can expose applications via Ingress.
Chef's notes 📓
One cluster I manage uses traefik Traefik for public services, but Nginx for internal management services such as Prometheus, etc. The idea is that you'd need one type of Ingress to help debug problems with the other type! ↩
Tip your waiter (sponsor) 👏
Did you receive excellent service? Want to compliment the chef? (..and support development of current and future recipes!) Sponsor me on Github / Ko-Fi / Patreon, or see the contribute page for more (free or paid) ways to say thank you! 👏
Employ your chef (engage) 🤝
Is this too much of a geeky PITA? Do you just want results, stat? I do this for a living - I'm a full-time Kubernetes contractor, providing consulting and engineering expertise to businesses needing short-term, short-notice support in the cloud-native space, including AWS/Azure/GKE, Kubernetes, CI/CD and automation.
Learn more about working with me here.
Flirt with waiter (subscribe) 💌
Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated.