Nginx Ingress Integrator
- By Tom Haddon
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 58 | 24 Mar 2023 | |
| 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:
At it’s core, Nginx Ingress Integrator is a basic charm that talks to the Kubernetes API and provisions an Nginx ingress resource.
In designing this charm, we’ve leveraged Juju’s sidecar pattern for Kubernetes charms, but somewhat unusually we’re not actually deploying a workload container alongside our charm code. Instead, the charm code is talking directly to the Kubernetes API to provision the appropriate Nginx ingress resource to enable traffic to reach the service in question.
As a result, if you run a kubectl get pods on a namespace named for the Juju model you’ve deployed the nginx-ingress-integrator charm into, you’ll see something like the following:
NAME READY STATUS RESTARTS AGE
nginx-ingress-integrator-0 1/1 Running 0 3h47m
This shows there is only one container, for the charm code itself.
Help us improve this documentation
Most of this documentation can be collaboratively discussed and changed on the respective topic in the doc category of the Charmhub forum. See the documentation guidelines if you’d like to contribute.