repeated ContainerStatus ephemeralContainerStatuses = 13;

  // Status of resources resize desired for pod's containers.
  // It is empty if no resources resize is pending.
  // Any changes to container resources will automatically set this to "Proposed"
  // +featureGate=InPlacePodVerticalScaling
  // +optional
  optional string resize = 14;
}

apps may target different 'environments' which contain different instances and variants of Istio.

- Better security: separate Istio components reside in different namespaces, allowing different teams or
roles to manage different parts of Istio. For example, a security team would maintain the
root CA and policy, a telemetry team may only have access to Prometheus,

Motivations to implement ztunnel generally came from two areas.

First, and most importantly, it serves as a means to implement the real goal: waypoints.
For various reasons outside the scope of this document, there is a desire to move from a sidecar based architecture to a "remote proxy" architecture.
However, this has one glaring issue: how do we get the traffic to the remote proxies, while maintaining the zero-trust properties that Istio is built upon?

properties: customMetric: description: Allows free-form specification of a metric. minLength: 1 type: string metric: description: One of the well-known Istio Standard Metrics. enum: - ALL_METRICS - REQUEST_COUNT - REQUEST_DURATION - REQUEST_SIZE - RESPONSE_SIZE - TCP_OPENED_CONNECTIONS - TCP_CLOSED_CONNECTIONS - TCP_SENT_BYTES - TCP_RECEIVED_BYTES - GRPC_REQUEST_MESSAGES - GRPC_RESPONSE_MESSAGES type: string mode: description: 'Controls which mode of metrics generation is selected: CLIENT and/or SERVER.'...