Traefik Ingress Operator for Kubernetes

Platform:

Channel Revision Published Runs on
latest/stable 344 Yesterday
Ubuntu 26.04 Ubuntu 20.04
latest/stable 343 Yesterday
Ubuntu 26.04 Ubuntu 20.04
latest/stable 333 24 Jun 2026
Ubuntu 26.04 Ubuntu 20.04
latest/candidate 344 Yesterday
Ubuntu 26.04 Ubuntu 20.04
latest/candidate 343 Yesterday
Ubuntu 26.04 Ubuntu 20.04
latest/candidate 333 24 Jun 2026
Ubuntu 26.04 Ubuntu 20.04
latest/beta 343 Yesterday
Ubuntu 26.04 Ubuntu 20.04
latest/beta 344 Yesterday
Ubuntu 26.04 Ubuntu 20.04
latest/beta 333 24 Jun 2026
Ubuntu 26.04 Ubuntu 20.04
latest/edge 345 Yesterday
Ubuntu 26.04 Ubuntu 20.04
latest/edge 344 Yesterday
Ubuntu 26.04 Ubuntu 20.04
latest/edge 343 Yesterday
Ubuntu 26.04 Ubuntu 20.04
latest/edge 342 Yesterday
Ubuntu 26.04 Ubuntu 20.04
1.0/stable 164 16 Feb 2024
Ubuntu 20.04
1.0/candidate 164 22 Nov 2023
Ubuntu 20.04
1.0/beta 164 22 Nov 2023
Ubuntu 20.04
1.0/edge 164 22 Nov 2023
Ubuntu 20.04
juju deploy traefik-k8s --channel 1.0/candidate

Learn about configurations >

  • 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 unit my-unit/2 in the my-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 unit my-unit/2 in the my-model model the following URL:

    http://my-model-my-unit-2.foo:8080