Nginx Ingress Integrator
- Canonical IS DevOps
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 120 | 24 Oct 2024 | |
| latest/stable | 121 | 24 Oct 2024 | |
| latest/stable | 101 | 28 May 2024 | |
| latest/edge | 123 | 25 Oct 2024 | |
| latest/edge | 122 | 25 Oct 2024 | |
| latest/edge | 109 | 22 Jul 2024 | |
| latest/edge | 44 | 16 Nov 2022 | |
| v2/edge | 84 | 09 Jan 2024 |
juju deploy nginx-ingress-integrator --channel edge
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.