Skip to content

Kubernetes Ingress Provider

Traefik can be configured to use Kubernetes Ingress as a provider.

See also Kubernetes user guide.


# Kubernetes Ingress Provider

# Enable Kubernetes Ingress Provider.

# Kubernetes server endpoint.
# Optional for in-cluster configuration, required otherwise.
# Default: empty
# endpoint = "http://localhost:8080"

# Bearer token used for the Kubernetes client configuration.
# Optional
# Default: empty
# token = "my token"

# Path to the certificate authority file.
# Used for the Kubernetes client configuration.
# Optional
# Default: empty
# certAuthFilePath = "/my/ca.crt"

# Array of namespaces to watch.
# Optional
# Default: all namespaces (empty array).
# namespaces = ["default", "production"]

# Ingress label selector to filter Ingress objects that should be processed.
# Optional
# Default: empty (process all Ingresses)
# labelselector = "A and not B"

# Value of `` annotation that identifies Ingress objects to be processed.
# If the parameter is non-empty, only Ingresses containing an annotation with the same value are processed.
# Otherwise, Ingresses missing the annotation, having an empty value, or the value `traefik` are processed.
# Optional
# Default: empty
# ingressClass = "traefik-internal"

# Disable PassHost Headers.
# Optional
# Default: false
# disablePassHostHeaders = true

# Enable PassTLSCert Headers.
# Optional
# Default: false
# enablePassTLSCert = true

# Throttle how frequently we refresh our configuration from Ingresses when there
# are frequent changes.
# Optional
# Default: 0 (no throttling)
# throttleDuration = 10s

# Override default configuration template.
# Optional
# Default: <built-in template>
# filename = "kubernetes.tmpl"

# Enable IngressEndpoint configuration.
# This will allow Traefik to update the status section of ingress objects, if desired.
# Optional
# [kubernetes.ingressEndpoint]
# At least one must be configured.
# `publishedservice` will override the `hostname` and `ip` settings if configured.
# hostname = "localhost"
# ip = ""
# publishedService = "namespace/servicename"


The Kubernetes server endpoint as URL.

When deployed into Kubernetes, Traefik will read the environment variables KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT to construct the endpoint.

The access token will be looked up in /var/run/secrets/ and the SSL CA certificate in /var/run/secrets/ Both are provided mounted automatically when deployed inside Kubernetes.

The endpoint may be specified to override the environment variable values inside a cluster.

When the environment variables are not found, Traefik will try to connect to the Kubernetes API server with an external-cluster client. In this case, the endpoint is required. Specifically, it may be set to the URL used by kubectl proxy to connect to a Kubernetes cluster using the granted authentication and authorization of the associated kubeconfig.


By default, Traefik processes all Ingress objects in the configured namespaces. A label selector can be defined to filter on specific Ingress objects only.

See label-selectors for details.


You can configure a static hostname or IP address that Traefik will add to the status section of Ingress objects that it manages. If you prefer, you can provide a service, which traefik will copy the status spec from. This will give more flexibility in cloud/dynamic environments.

TLS communication between Traefik and backend pods

Traefik automatically requests endpoint information based on the service provided in the ingress spec. Although traefik will connect directly to the endpoints (pods), it still checks the service port to see if TLS communication is required.

There are 3 ways to configure Traefik to use https to communicate with backend pods:

  1. If the service port defined in the ingress spec is 443 (note that you can still use targetPort to use a different port on your pod).
  2. If the service port defined in the ingress spec has a name that starts with https (such as https-api, https-web or just https).
  3. If the ingress spec includes the annotation https.

If either of those configuration options exist, then the backend communication protocol is assumed to be TLS, and will connect via TLS automatically.


Please note that by enabling TLS communication between traefik and your pods, you will have to have trusted certificates that have the proper trust chain and IP subject name. If this is not an option, you may need to skip TLS certificate verification. See the insecureSkipVerify setting for more details.


General annotations

The following general annotations are applicable on the Ingress object:

Annotation Description "/index.html" Redirects all requests for / to the defined path. (1) <YML> See custom error pages section. (2) http,https Override the default frontend endpoints. <YML> Forward the client certificate following the configuration in YAML. (3) "true" Override the default frontend PassTLSCert value. Default: false.(DEPRECATED) "true" Forward client Host header to the backend. "3" Override the default frontend rule priority. <YML> See rate limiting section. (4) https Enables Redirect to another entryPoint for that frontend (e.g. HTTPS). "true" Return 301 instead of 302. ^http://localhost/(.*) Redirect to another URL for that frontend. Must be set with http://mydomain/$1 Redirect to another URL for that frontend. Must be set with AddPrefix: /users Adds a request modifier to the backend request. /users Replaces each matched Ingress path with the specified one, and adds the old path to the X-Replaced-Path header. PathPrefixStrip Overrides the default frontend rule type. Only path-related matchers can be specified (Path, PathPrefix, PathStrip, PathPrefixStrip).(5) <YML> Set ingress backend weights specified as percentage or decimal numbers in YAML. (6) ", fe80::/16" A comma-separated list of IP ranges permitted for access (7). "true" Use X-Forwarded-For header as valid source of IP for the white list.<NAME> Set the protocol Traefik will use to communicate with pods. Acceptable protocols: http,https,h2c

<1> Non-root paths will not be affected by this annotation and handled normally. This annotation may not be combined with other redirect annotations. Trying to do so will result in the other redirects being ignored. This annotation can be used in combination with to configure whether the app-root redirect is a 301 or a 302.

<2> example:

  - "404"
  backend: bar
  query: /bar
  - "503"
  - "500"
  backend: bar
  query: /bir

<3> example:

# add escaped pem in the `X-Forwarded-Tls-Client-Cert` header
pem: true
# add escaped certificate following infos in the `X-Forwarded-Tls-Client-Cert-Infos` header
  notafter: true
  notbefore: true
  sans: true
    country: true
    province: true
    locality: true
    organization: true
    commonname: true
    serialnumber: true

If pem is set, it will add a X-Forwarded-Tls-Client-Cert header that contains the escaped pem as value. If at least one flag of the infos part is set, it will add a X-Forwarded-Tls-Client-Cert-Infos header that contains an escaped string composed of the client certificate data selected by the infos flags. This infos part is composed like the following example (not escaped):

Subject="C=FR,ST=SomeState,L=Lyon,O=Cheese,CN=*",NB=1531900816,NA=1563436816,SAN=*,*,,[email protected],[email protected],,

Note these options work only with certificates issued by CAs included in the applicable EntryPoint ClientCA section; certificates from other CAs are not parsed or passed through as-is.

<4> example:

extractorfunc: client.ip
    period: 3s
    average: 6
    burst: 9
    period: 6s
    average: 12
    burst: 18

<5> Note: ReplacePath is deprecated in this annotation, use the annotation instead. Default: PathPrefix.

<6> Service weights enable to split traffic across multiple backing services in a fine-grained manner.


service_backend1: 12.50%
service_backend2: 12.50%
service_backend3: 75 # Same as 75%, the percentage sign is optional

A single service backend definition may be omitted; in this case, Traefik auto-completes that service backend to 100% automatically. Conveniently, users need not bother to compute the percentage remainder for a main service backend. For instance, in the example above service_backend3 does not need to be specified to be assigned 75%.


For each service weight given, the Ingress specification must include a backend item with the corresponding serviceName and (if given) matching path.

Currently, 3 decimal places for the weight are supported. An attempt to exceed the precision should be avoided as it may lead to percentage computation flaws and, in consequence, Ingress parsing errors.

For each path definition, this annotation will fail if:

  • the sum of backend weights exceeds 100% or
  • the sum of backend weights is less than 100% without one or more omitted backends

See also the user guide section traffic splitting.

<7> All source IPs are permitted if the list is empty or a single range is ill-formatted. Please note, you may have to set service.spec.externalTrafficPolicy to the value Local to preserve the source IP of the request for filtering. Please see this link for more information.


Please note that and do not have to be set if is defined for the redirection (they will not be used in this case).

The following annotations are applicable on the Service object associated with a particular Ingress object:

Annotation Description <YML> (1) See the buffering section.
traefik.backend.loadbalancer.sticky: "true" Enable backend sticky sessions (DEPRECATED). "true" Enable backend sticky sessions. <expression> Set the circuit breaker expression for the backend. "10ms Defines the interval between two flushes when forwarding response from backend to client. drr Override the default wrr load balancer algorithm. "10" Sets the maximum number of simultaneous connections to the backend.
Must be used in conjunction with the label below to take effect. client.ip Set the function to be used against the request to determine what to limit maximum connections to the backend by.
Must be used in conjunction with the above label to take effect. <NAME> Manually set the cookie name for sticky sessions.

<1> example:

maxrequestbodybytes: 10485760
memrequestbodybytes: 2097153
maxresponsebodybytes: 10485761
memresponsebodybytes: 2097152
retryexpression: IsNetworkError() && Attempts() <= 2

Note and are supported prefixes.

Custom Headers Annotations

Annotation Description EXPR Provides the container with custom request headers that will be appended to each request forwarded to the container. Format: HEADER:value||HEADER2:value2 EXPR Appends the headers to each response returned by the container, before forwarding the response to the client. Format: HEADER:value||HEADER2:value2

Security Headers Annotations

The following security annotations are applicable on the Ingress object:

Annotation Description EXPR Provides a list of allowed hosts that requests will be processed. Format: Host1,Host2 "true" Adds the X-XSS-Protection header with the value 1; mode=block. VALUE Adds CSP Header with the custom value. "true" Adds the X-Content-Type-Options header with the value nosniff. VALUE Set custom value for X-XSS-Protection header. This overrides the BrowserXssFilter option. VALUE Overrides the X-Frame-Options header with the custom value. "false" Adds the STS header to non-SSL requests. "true" Adds the X-Frame-Options header with the value of DENY. "315360000" Sets the max-age of the HSTS header. "true" Adds the IncludeSubdomains section of the STS header. "true" Adds the preload flag to the HSTS header. "false" This will cause the AllowedHosts, SSLRedirect, and STSSeconds/STSIncludeSubdomains options to be ignored during development.
When deploying to production, be sure to set this to false. EXPR Provides a list of headers that the proxied hostname may be stored. Format: HEADER1,HEADER2 VALUE Adds HPKP header. VALUE Adds referrer policy header. "true" Forces the frontend to redirect to SSL if a non-SSL request is sent. "true" Forces the frontend to redirect to SSL if a non-SSL request is sent, but by sending a 302 instead of a 301. HOST This setting configures the hostname that redirects will be based on. Default is "", which is the same host as the request. "true" If SSLForceHost is true and SSLHost is set, requests will be forced to use SSLHost even the ones that are already using SSL. Default is false. EXPR Header combinations that would signify a proper SSL Request (Such as X-Forwarded-Proto:https). Format: HEADER:value||HEADER2:value2


Additional authentication annotations can be added to the Ingress object. The source of the authentication is a Secret object that contains the credentials.

Annotation basic digest forward Description basic x x x Contains the authentication type: basic, digest, forward. mysecret x x Name of Secret containing the username and password with access to the paths defined in the Ingress object. true x x If set to true removes the Authorization header. X-WebAuth-User x x Pass Authenticated user to application via headers. x The URL of the authentication server. false x Trust X-Forwarded-* headers. X-Auth-User, X-Secret x Copy headers from the authentication server to the request. secret x Name of Secret containing the certificate and key for the forward auth. x If set to true invalid SSL certificates are accepted.

The secret must be created in the same namespace as the Ingress object.

The following limitations hold for basic/digest auth:

  • The realm is not configurable; the only supported (and default) value is traefik.
  • The Secret must contain a single file only.

TLS certificates management

TLS certificates can be managed in Secrets objects. More information are available in the User Guide.


Only TLS certificates provided by users can be stored in Kubernetes Secrets. Let's Encrypt certificates cannot be managed in Kubernets Secrets yet.

Global Default Backend Ingresses

Ingresses can be created that look like the following:

apiVersion: extensions/v1beta1
kind: Ingress
  name: cheese
    serviceName: stilton
    servicePort: 80

This ingress follows the Global Default Backend property of ingresses. This will allow users to create a "default backend" that will match all unmatched requests.


Due to Traefik's use of priorities, you may have to set this ingress priority lower than other ingresses in your environment, to avoid this global ingress from satisfying requests that could match other ingresses. To do this, use the annotation (as seen in General Annotations) on your ingresses accordingly.