Interesting. I was recently building something similar but I went for Istio with VMs (where VM is more like an unmanaged process rather than an actual VM). Not only I can route to the cluster from the local dev, the cluster routes to my local dev. Full mTLS, subject to every possible traffic shaping solution available in Istio, vcluster, no vcluster, multi-cluster mesh, what have you. Since we use Istio everywhere this approach means there are no new tools.
Thanks for sharing:) Your approach seems reasonable and extremely powerful for variable features. As you mentioned, using local Envoy proxy with Istio is an excellent choice. But my approach was for reducing all the extra setups and just ‘port-forward’ services with single binary. I was intended to help developers who might be less experienced with cloud-native complexities, or anyone who just wants a simple way to do testing against their clusters!
Thoughts on providing pre-compiled releases? I’m at a TS/node shop and while I can compile go, getting the team to adopt this is a lot harder if step one is to install go, step two is clone a repo they’ll only need for building, etc.
Thanks for the feedback. I’ll support brew tap / install today or tomorrow:)
Check README.md please. brew install now supported!