Traefik Ingress Operator for Kubernetes
- Canonical Observability
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 203 | 03 Dec 2024 | |
latest/candidate | 218 | 03 Dec 2024 | |
latest/beta | 223 | 03 Dec 2024 | |
latest/edge | 224 | 04 Dec 2024 | |
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/candidate
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 Traefik ingress. If unspecified, the gateway ingress ip address will be used, e.g, as provided by MetalLB. This needs to be a
bare
hostname: 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://foo
external URL, will provide to the unitmy-unit/2
in themy-model
model the following URL:http://foo/my-model-my-unit-2
With 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:8080
external URL, will provide to the unitmy-unit/2
in themy-model
model the following URL:http://my-model-my-unit-2.foo:8080