Daniel Loader

On the note of an operator, some sort of capacity to define a client either providing the secret externally or exporting the secret back out to a kubernetes secret option...

This would probably affect me if I were not already blocked by this [issue](https://github.com/metalbear-co/mirrord/issues/1618)

https://github.com/rofl0r/microsocks works too, handy given it's on homebrew and most linux package managers out the box. Alternatively I've had fun with `mirrord exec -- zsh` and then being able to...

Yeah this has hit me before too, good to see an issue raised.

To extend this conversation, I've got mirrord working happily inside a docker container, but I'd like to expose the application that's tunnelled to the rest of the local network namespace....

Can confirm this also affects linux users too, though not surprised it's not a platform specific issue. Don't want to overstate it but it's a showstopper for using this plugin...

This would be great for moving the email sending capabilities out to a microservice to render/send it via sendgrid etc.

Can confirm just trying to deploy chart with tls via the ingress yields the same issue as the original issue post.

Likewise this bit me instantly when trying to use tolerations to tolerate my core managed node group on EKS and not just provision karpenter provisioned nodes just for the sake...

You might be able to combine kube-fledged with https://github.com/XenitAB/spegel to get this behaviour.