feat(DestinationRules): Adding aggression and min_weight_percent to DestinationRules API

networking/v1alpha3/destination_rule.proto

@@ -377,6 +377,7 @@ message Subset {
 // ```
 //
 message LoadBalancerSettings {
+  // +kubebuilder:validation:XValidation:message="only one of warmupDurationSecs or warmup can be set",rule="(has(self.warmupDurationSecs)?1:0)+(has(self.warmup)?1:0)<=1"
   // Standard load balancing algorithms that require no tuning.
   enum SimpleLB {
     // No load balancing algorithm has been specified by the user. Istio
@@ -514,9 +515,20 @@ message LoadBalancerSettings {
   // 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.
+  // Deprecated: use `warmup` instead.
   google.protobuf.Duration warmup_duration_secs = 4;
+
+  WarmupConfiguration warmup = 5;
 }
 
+message WarmupConfiguration {
+  google.protobuf.Duration duration = 1;
+  // +kubebuilder:validation:Maximum=100
+  // +kubebuilder:validation:Minimum=0
+  google.protobuf.DoubleValue minimum_percent = 2;
+  // +kubebuilder:validation:Minimum=0
+  google.protobuf.DoubleValue aggression = 3;
+}
 // Connection pool settings for an upstream host. The settings apply to
 // each individual host in the upstream service.  See Envoy's [circuit
 // breaker](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/circuit_breaking)

releasenotes/notes/slow-start-aggression-minimum-percent-parameters.yaml

@@ -0,0 +1,13 @@
+apiVersion: release-notes/v2
+
+kind: feature
+area: traffic-management
+issue:
+- 3215
+
+releaseNotes:
+- |
+    **Added** aggression and minimum_percent parameters
+
+docs:
+  - https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/slow_start