mirror of
https://github.com/fluxcd/flagger.git
synced 2026-04-15 06:57:34 +00:00
support WarmupDurationSecs
Signed-off-by: S-mishina <seiryu.mishina@zozo.com> Delete unwanted descriptions Signed-off-by: S-mishina <seiryu.mishina@zozo.com> Add kustomize/base/flagger/crd.yaml WarmupDurationSecs field Signed-off-by: S-mishina <seiryu.mishina@zozo.com> fix warmupDurationSecs description Signed-off-by: S-mishina <seiryu.mishina@zozo.com>
This commit is contained in:
@@ -255,6 +255,15 @@ type LoadBalancerSettings struct {
|
||||
// Locality load balancer settings, this will override mesh wide settings in entirety, meaning no merging would be performed
|
||||
// between this object and the object one in MeshConfig
|
||||
LocalityLbSetting *LocalityLbSetting `json:"localityLbSetting,omitempty"`
|
||||
// Represents the warmup duration of Service. If set, the newly created endpoint of service
|
||||
// remains in warmup mode starting from its creation time for the duration of this window and
|
||||
// Istio progressively increases amount of traffic for that endpoint instead of sending proportional amount of traffic.
|
||||
// This should be enabled for services that require warm up time to serve full production load with reasonable latency.
|
||||
// Please note that this is most effective when few new endpoints come up like scale event in Kubernetes. When all the
|
||||
// endpoints are relatively new like new deployment, this is not very effective as all endpoints end up getting same
|
||||
// amount of requests.
|
||||
// Currently this is only supported for ROUND_ROBIN and LEAST_REQUEST load balancers.
|
||||
WarmupDurationSecs string `json:"warmupDurationSecs,omitempty"`
|
||||
}
|
||||
|
||||
// Locality-weighted load balancing allows administrators to control the
|
||||
|
||||
Reference in New Issue
Block a user