Harvey Xia

I'm looking for this very feature, are there any plans for implementing it in the near future?

TODOs: 1. Garbage collect resources originating from extension servers

This requires changes to relay architecture, is significant amount of work and carries the risk of destabilizing the product, so we need to achieve alignment on the priority of this...

Discussed this offline a bit, the solution may be somewhat involved depending on which UX we choose. **Approach 1: Lock the latest good state of applied policies** For a given...

> In this example, the outlierDetection should only apply to requests coming from the istio-system namespace. To my knowledge, there's no way to have DestinationRule config apply selectively per source....

Expanding on this issue: **Motivation** We've received some customer interest in the ability to defined DestinationRule config at a per-source granularity. Specifically, one customer has a use case where they...

This can be prevented by enabling conflict detection, which you can do by passing the `disallowIntersectingConfig=true` CLI argument to the Gloo Mesh networking deployment on OSS or the enterprise-networking deployment...

Additionally, we should add a `meshctl` command that can verify that relay server and agent certs are compatible.

I am also interested in this feature—we want to use our own tooling for managing instance rotation for existing ASGs, and Cluster API for managing the lifecycle of the ASG...

I'm having the same issue. I'm also unable to access the kube-apiserver via the capg-managed LB because the health check is failing (targeting port 6443), which in turn is failing...