John Howard
John Howard
I am actually not entirely sure you can remove it now that I think about it. In other types (EDS, RDS), as far as I know, even an explicit DELETE...
related: https://github.com/istio/istio/issues/47838
This is caused by https://github.com/istio/ztunnel/blob/f9272ec8100c4526a1695e2cf84f8f8863a1f1b0/src/proxy/inbound.rs#L293 which is needed until we implement https://docs.google.com/document/d/1Lk1I1qB-XwVWFP0sVcIN5JMJZHjuF3j8lGWtUeDK6pY/edit#heading=h.nluvz4y67j4c properly which clearly delineates ztunnel policies from ambient policies
The full implementation merged recently in 1.29 alpha On Mon, Nov 6, 2023, 11:03 PM Istio Policy Bot ***@***.***> wrote: > 🧭 This issue or pull request has been automatically...
> Per-direction customization seems like a really complex potential footgun - what would be a valid scenario for that? Most obvious case I can think of is I run Nginx...
> > > Per-direction customization seems like a really complex potential footgun - what would be a valid scenario for that? > > > > > > Most obvious case...
Port annotations (in their current impl) do allow you to enable up/down redirect exclusion, as you can do `includeInboundPorts: *` etc
DISABLE in ambient does not actually disable capture, it is ignored/deprecated On Tue, Aug 15, 2023 at 8:02 AM Ben Leggett ***@***.***> wrote: > exclude/includePorts is as far as I...