steeling

Yes it does!

Let's just repurpose this issue as the design doc?

I'll add that https://github.com/openservicemesh/osm/issues/4862 and https://github.com/openservicemesh/osm/issues/4863 have implications in how we will change: * Endpoints providers * Internal MeshCatalog representations like Policy objects * K8s clients * Possibly other internals...

As a heads up, we've allocated #4862 to our v1.3 release. I think trying to apply another layer of refactoring/abstraction simultaneously would lead to the incorrect layers of abstraction being...

Commeting here for posterity, but https://github.com/openservicemesh/osm/pull/5109 tackles this decoupling in a different way. https://github.com/openservicemesh/osm/issues/5112 will help move that forward too. Note that now the envoy.Proxy object contains no specific envoy...

We should probably default this to run as non-root. If we did this, do you need further customization?

approved! please make sure tests pass before submitting :)

Ya, closing out

This can be split into multiple tasks, namely, 1. Configurator 2. MeshCataloger 3. k8s.Controller 4. providers/kube

A lot of work has been done here. some of the remaining steps: Remove all instances of k8s.Controller, except for the usage in `pkg/compute/kube`. To do this, we'll likely have...