mirror of
https://github.com/funkypenguin/geek-cookbook/
synced 2025-12-15 10:46:34 +00:00
601e9cdd73
* Updated instructions to match new repo layout * Updating file paths to match the new repo organization * Updated one reference from /flux-system to /bootstrap * Changed one more reference to /flux-system to /bootstrap * Typo * Added requested formatting and missing backslash in bootstrap command. Co-authored-by: David Young <davidy@funkypenguin.co.nz>
20 lines
942 B
Markdown
20 lines
942 B
Markdown
---
|
|
description: What is a Kubernetes Ingress?
|
|
---
|
|
# Ingresses
|
|
|
|
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][radarr] pod, but <https://sonarr.example.com> will end up on a [Sonarr][sonarr] pod.
|
|
|
|
|
|
|
|
There are many popular Ingress Controllers, we're going to cover two equally useful options:
|
|
|
|
1. [Traefik](/kubernetes/ingress/traefik/)
|
|
2. [Nginx](/kubernetes/ingress/nginx/)
|
|
|
|
Choose at least one of the above (*there may be valid reasons to use both!* [^1]), so that you can expose applications via Ingress.
|
|
|
|
--8<-- "recipe-footer.md"
|
|
|
|
[^1]: 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!
|