// current contains the current value for the given metric
  optional MetricValueStatus current = 2;
}

// HPAScalingPolicy is a single policy which must hold true for a specified past interval.
message HPAScalingPolicy {
  // type is used to specify the scaling policy.
  optional string type = 1;

  // value contains the amount of change which is permitted by the policy.

  // current contains the current value for the given metric
  optional MetricValueStatus current = 2;
}

// HPAScalingPolicy is a single policy which must hold true for a specified past interval.
message HPAScalingPolicy {
  // type is used to specify the scaling policy.
  optional string type = 1;

  // value contains the amount of change which is permitted by the policy.

  held off after the release. Hiding/Showing documentation does not require TOC approval.
* Cases for other API changes require TOC approval
    * Simple `meshConfig` changes have been approved in the past. Functionality should not be enabled by default.
* For large API changes, 2 members of the TOC must approve the PR before release manager approval in the release branch

flexibility. - the dedicated pilot-per-ingress is required if the gateway needs to support k8s-style ingress. # Port and basic host configuration In order to configure the Service object, the install/upgrade needs to provide a list of all ports. In the past, this was done when installing/upgrading full istio, and involved some duplication - ports configured both in upgrade, Gateway and VirtualService. The new Ingress chart uses a 'values.yaml' (see user-example-ingress), which auto-generates Service ports,...

# Port and basic host configuration

In order to configure the Service object, the install/upgrade needs to provide a list of all ports.
In the past, this was done when installing/upgrading full istio, and involved some duplication - ports configured
both in upgrade, Gateway and VirtualService.