SD-Core

  • Canonical Telco | bundle
Channel Revision Published
latest/beta 8 04 Jan 2024
latest/edge 9 04 Jan 2024
1.3/beta 13 24 Jan 2024
1.3/edge 28 28 Nov 2024
juju deploy sdcore-k8s --channel 1.3/edge
Show information

Platform:

Learn about configurations >

  • enable_experimental_forward_auth | boolean

    Enables `forward-auth` middleware capabilities required to set up Identity and Access Proxy. This feature is experimental and may be unstable.

  • 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`

  • tls-ca | string

    CA cert used for TLS termination.

  • tls-cert | string

    SSL cert used for TLS termination.

  • tls-key | string

    Key used for TLS termination.