Istio Ingress
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 1/stable | 33 | 26 Jun 2025 | |
| 1/candidate | 33 | 10 Jun 2025 | |
| 1/beta | 33 | 10 Jun 2025 | |
| 1/edge | 33 | 14 May 2025 | |
| 2/candidate | 50 | 08 Oct 2025 | |
| 2/edge | 50 | 11 Sep 2025 |
juju deploy istio-ingress-k8s --channel 1/stable
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
-
external_hostname | string
The DNS name to be used by Istio ingress. If unspecified, the gateway ingress ip address will be used, e.g, as provided by MetalLB. This needs to be a
barehostname: i.e. no schema prefix and no port. Hostname can be “precise” which is a domain name without the terminating dot of a network host (e.g. “foo.example.com”). It's also important to note that domain name prefixed with a single wildcard label (e.g. *.example.com) isn't supported for now. -
ready-timeout | int
Default: 100
The maximum time (in seconds) to wait for the gateway deployment to be ready. This applies specifically to the deployment/LB created for the Istio gateway controller. If the deployment does not become ready within this time, charm will go into blocked state.