Shashank Ram

Hey @naqvis, thanks for the detailed proposal. This is definitely an interesting topic worth reviewing and discussing in greater detail. I am wondering if you would be able to draft...

Good point @grampelberg on giving the destination ownership over deciding which sources are allowed to talk to it. However without a namespace, how would the service mesh implementation differentiate destinations...

This seems like a regression as the [code](https://github.com/openservicemesh/osm/blob/main/pkg/k8s/announcement_handlers.go) should handle the cleanup of secrets via k8s garbage collection through OwnerReferences. /cc @jaellio

> A user in namespace `default` with RBAC restrictions restricting users to that namespace should not be able to create a TrafficTarget allowing traffic out of that namespace and into...

> I would like for OSM controller to generate these configs based on the existing configuration. It seems that everything needed is already there and OSM should be able to...

> It would be interesting to have such a feature into the Helm chart. @nlamirault Thanks for opening this issue. Could you describe in the issue why this is required...

@steeling I don't have a strong opinion on whether we want to repurpose this issue or create a new issue to allow a mechanism to directly configure Envoy. This is...

Hey @mudit-01, this PR has some conflicts with the version in `main`. Would you mind rebasing/merging your changes with the main branch.

> I thought about re-architecting the demo app down to a single view to show all the activity. I'm thinking we should decouple it from the build as well as...

@steeling could you please describe in detail the motivation for this issue and what is being requested here. Does this pertain to egress (pod to external) traffic or something else?