kubectl

> context.Background() is typically only used when one doesn’t care about the result. If you did care about the result, you should be passing the parent context to preserve the circuit breaker timeout in case the operation takes too long. Not true in my experience. You would use context.Background in a test situation. It's also commonly used for short-lived applications like a CLI. You can see kubectl uses context.Background quite a lot: https://github.com/kubernetes/kubectl/search?q=context.backg... > I think the level of pain you experience from mutable references in Rust depends on if you’re coming from an OOP or FP background. I have a FP background and so the patterns I use to build code already greatly restrict mutation. You can usually change code that updates data immutably (creating a new copy of it) with mutable code in rust be

This is entirely to hard to find the answer to in the kubernetes/kubectl documentation. Apparently the forward is done via socat over tls: https://stackoverflow.com/questions/50645059/is-kubectl-port... And socat is mentioned in: https://github.com/kubernetes/kubectl/blob/master/pkg/cmd/po... I didn't actually manage to find out what or how socat is called - but I'm also on mobile, so it's a little convoluted to browse source code. Anyone know where the call to socat happens, after kubectl port-forward?