Nginx Ingress Integrator
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 203 | 09 Sep 2025 | |
| latest/stable | 202 | 09 Sep 2025 | |
| latest/stable | 144 | 09 Sep 2025 | |
| latest/stable | 145 | 09 Sep 2025 | |
| latest/stable | 101 | 28 May 2024 | |
| latest/edge | 473 | Today | |
| latest/edge | 471 | 02 May 2026 | |
| latest/edge | 145 | 13 Mar 2025 | |
| latest/edge | 144 | 13 Mar 2025 | |
| latest/edge | 109 | 22 Jul 2024 | |
| v2/edge | 84 | 09 Jan 2024 |
juju deploy nginx-ingress-integratorOur docs have moved to a new home!
Please update your bookmarks, and contact us if you have any questions.
A Juju charm deploying and managing external access to HTTP/HTTPS services in a Kubernetes cluster via an Nginx Ingress resource. This requires the Kubernetes cluster in question to have an Nginx Ingress Controller already deployed into it.
This charm simplifies exposing services running inside a Kubernetes cluster to external clients. It offers TLS termination as well as easy configuration of a number of advanced features including rate limiting, restricting access to specific client IP source ranges, and OWASP ModSecurity Core Rule Set (CRS).
As such, the charm makes it easy for charm developers to provide external access to their HTTP workloads in Kubernetes by easy integration offered via the charm’s nginx_route library.
For DevOps and SRE teams, providing ingress for charms that support a relation to this charm will be possible via a simple juju relate command.