stepWeightPromotion
is specified, the promotion phase happens in stages, the traffic is routed back to the primary pods in a progressive manner, the primary weight is increased until it reaches 100%.spec.skipAnalysis: true
. When skip analysis is enabled, Flagger checks if the canary deployment is healthy and promotes it without analysing it. If an analysis is underway, Flagger cancels it and runs the promotion.stepWeights
- determines the ordered array of weights, which shall be used during canary promotion.stepWeights
values till 80.
We would have steps (canary weight : primary weight):maxWeight
and stepWeight
settings.exact: "value"
for exact string matchprefix: "value"
for prefix-based matchsuffix: "value"
for suffix-based matchsourceLabels
match conditions are applicable only when the mesh
gateway is included in the canary.service.gateways
list.always
. Starting with NGINX ingress v0.31, regex matching is supported for header values.stepWeight/maxWeight
with iterations
in the analysis
spec:spec.analysis.mirror
to true
.