Traefik 2.2.0 → 2.3.0
11 versions, 5 migration-guide sections in 2 versions, 0 required stops
Version by version, oldest first
2.2.1 – 2.2.4: no action items (4 versions)
2.2.5 2020-07-13
Migration
InsecureSNI removal
In v2.2.2 we introduced a new flag (insecureSNI) which was available as a global option to disable domain fronting. Since v2.2.5 this global option has been removed, and you should not use it anymore.
From doc.traefik.io/traefik/v2.11/migration/v2/#insecuresni-removal
Migration
HostSNI rule matcher removal
In v2.2.2 we introduced a new rule matcher (HostSNI) for HTTP routers which was allowing to match the Server Name Indication at the router level. Since v2.2.5 this rule has been removed for HTTP routers, and you should not use it anymore.
From doc.traefik.io/traefik/v2.11/migration/v2/#hostsni-rule-matcher-removal
2.2.6 – 2.2.11: no action items (5 versions)
2.3.0 2020-09-23
Migration
X.509 CommonName Deprecation
The deprecated, legacy behavior of treating the CommonName field on X.509 certificates as a host name when no Subject Alternative Names are present, is now disabled by default.
It means that if one is using https with your backend servers, and a certificate with only a CommonName, Traefik will not try to match the server name indication with the CommonName anymore.
It can be temporarily re-enabled by adding the value x509ignoreCN=0 to the GODEBUG environment variable.
More information: https://golang.org/doc/go1.15#commonname
From doc.traefik.io/traefik/v2.11/migration/v2/#x509-commonname-deprecation
Migration
File Provider
The file parser has been changed, since v2.3 the unknown options/fields in a dynamic configuration file are treated as errors.
From doc.traefik.io/traefik/v2.11/migration/v2/#file-provider
Migration
IngressClass
In v2.3, the support of IngressClass, which is available since Kubernetes version 1.18, has been introduced. In order to be able to use this new resource the Kubernetes RBAC must be updated.
From doc.traefik.io/traefik/v2.11/migration/v2/#ingressclass
Release notes from github.com/traefik/traefik/blob/master/CHANGELOG.md, and Migration: Steps needed between the versions (v2.11 documentation), checked 17 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important note, is shown; read the full notes for anything else. Traefik's release notes (CHANGELOG.md, GitHub releases) are lists of merged pull requests and mark nothing as breaking. What is quoted instead is Traefik's migration documentation on doc.traefik.io: “Migration: Steps needed between the versions” (v3), the same page of the v2.11 documentation (v2), and “Configuration Details for Migrating from Traefik v2 to v3” (on 3.0.0). Each section of those pages is labelled “Migration” and shown on the release its heading names (“v3.3 to v3.4” on 3.4.0). A section naming a canceled release (v2.4.10, v2.9.0) is shown on the next release of that line. Versions are covered from 2.0.0. No required stop is documented.