Comment 6 for bug 1847084

Tim's answer above is relevant to charm deployed workloads, but one thing he didn't realise is that we don't currently run the proxy update worker in a k8s controller. So the controller internals, including the bit that connects to the charm store, do not use a configured proxy.

Whether proxy env vars are the best approach in general for k8s is a point that needs considering, as opposed to possibly more idiomatic solutions. As a workaround for now, you could try:

1. bootstrap the controller
2. edit the controller statefulset to amend the podspec to include the proxy env vars
3. let k8s restart the controller pod
4. check that the controller pod has the proxy env vars set and try a deploy again