Shashank Ram

Hey @keithmattix, that's an interesting ask. One of the most basic requirements of permissive mode is to bootstrap application connectivity across the entire mesh with no configuration to simplify the...

> Sure thing! > > So essentially, OSM has two different trust models by default: > > 1. everything's trusted > 2. nothing's trusted > > My proposal is to...

> @shashankram no - I think the we keep things simple and not try to handle the cross-namespace case. That's a security issue waiting to happen, and at that point,...

@stefanprodan How does this proposal handle the use case where we want a combination of TCP and HTTP routes for an endpoint while ensuring no ambiguity? For ex. HTTP GET...

Here's some context from the time we introduced this feature: The initial idea to support multiple meshes was to address multi-tenancy within the same cluster and provide isolation primitives in...

> Multiple CI runs is an interesting case, although I'd imagine that applies to us more so than to customers? If so, it seems like what we have with KIND...

@dasMulli OSM does not support ingress (traffic from clients outside the cluster) for raw TCP traffic. Currently, OSM only supports HTTP and HTTPS ingress. Refer to the [ingress guide](https://release-v1-0.docs.openservicemesh.io/docs/guides/traffic_management/ingress/) to...

> Discussed this with @steeling over a call, but another option is to get rid of the crdconversion webhook (and server) entirely. If we look at the conversionHandler methods for...

> Currently the conversion webhook does nothing however, except cause bugs and headaches. I recommend that, if and when, we ever need to drop a field, we can revisit how...

Let's discuss this before working on the task. I don't think we need to spin up a controller within the CLI just to make fetch objects from the API server.