Traefik Ingress Operator for Kubernetes
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 281 | 30 Mar 2026 | |
| latest/candidate | 283 | 30 Mar 2026 | |
| latest/beta | 283 | 30 Mar 2026 | |
| latest/edge | 292 | 30 Apr 2026 | |
| 1.0/stable | 164 | 16 Feb 2024 | |
| 1.0/candidate | 164 | 22 Nov 2023 | |
| 1.0/beta | 164 | 22 Nov 2023 | |
| 1.0/edge | 164 | 22 Nov 2023 |
juju deploy traefik-k8s --channel 1.0/stable
-
external_hostname | string
The DNS name to be used by Traefik 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. -
routing_mode | string
Default: path
The routing mode allows you to specify how Traefik going to generate routes on behalf of the requesters.
Valid values are "path" and "subdomain".
With the "path" routing mode, Traefik will use its externally-visible url, and create a route for the requester that will be structure like:
<external_url>/<requester_model_name>-<requester_application_name>-<requester-unit-index>For example, an ingress-per-unit provider with
http://fooexternal URL, will provide to the unitmy-unit/2in themy-modelmodel the following URL:http://foo/my-model-my-unit-2With the "subdomain" routing mode, Traefik will use its externally-visible url, and create a route for the requester that will be structure like:
<protocol>://<requester_model_name>-<requester_application_name>-<requester-unit-index>.<external_hostname>:<port>/For example, an ingress-per-unit provider with
http://foo:8080external URL, will provide to the unitmy-unit/2in themy-modelmodel the following URL:http://my-model-my-unit-2.foo:8080