NGINX ingress integrator charm¶
A Juju charm deploying and managing external access to HTTP/HTTPS services in a Kubernetes cluster through 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 through 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 through a simple juju relate command.
In this documentation¶
Tutorials Get started - a hands-on introduction to using the NGINX ingress integrator for new users |
How-to guides Step-by-step guides covering key operations and common tasks |
Reference Technical information - specifications, APIs, architecture |
Explanation Concepts - discussion and clarification of key topics |
Contributing to this documentation¶
Documentation is an important part of this project, and we take the same open-source approach to the documentation as the code. As such, we welcome community contributions, suggestions, and constructive feedback on our documentation. See How to contribute for more information.
If there’s a particular area of documentation that you’d like to see that’s missing, please file a bug.
Project and community¶
The NGINX ingress integrator charm 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 charm for your next project? Get in touch!