Nginx Ingress Integrator
- By Tom Haddon
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 58 | Yesterday | |
| latest/edge | 59 | Yesterday |
juju deploy nginx-ingress-integrator
You will need Juju 2.9 to be able to run this command. Learn how to upgrade to Juju 2.9.
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
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 ingress 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.
Project and community
The Nginx Ingress Integrator Operator is a member of the Ubuntu family. It's an open source project that warmly welcomes community projects, contributions, suggestions, fixes and constructive feedback.
Thinking about using the Nginx Ingress Integrator for your next project? Get in touch!
For further details, see the charm's detailed documentation.