homelab/traefik
1
0
Fork 0
Code Activity

Add a k8s guide section on traffic splitting via service weights.

Browse source
This commit is contained in:
Timo Reimann 2018-07-03 16:50:06 +02:00 • committed by Traefiker Bot
parent 31a8e3e39a
commit 41eb4f1c70
2 changed files with 85 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/configuration/backends/kubernetes.md
View file

@ -209,7 +209,6 @@ Trying to do so leads to an error and the corresponding Ingress object being ign
<5> `traefik.ingress.kubernetes.io/service-weights`:
Service weights enable to split traffic across multiple backing services in a fine-grained manner.
A canonical use case are canary releases where a new deployment starts to receive a small percentage of traffic (e.g., 1%) and steadily increases over time as confidence in the new deployment improves.
Example:
@ -234,6 +233,8 @@ 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](/user-guide/kubernetes/#traffic-splitting).
<6> `traefik.ingress.kubernetes.io/whitelist-source-range`:
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.