Apply HTTP proxy configuration across the all future pods

[yhaliaw]

Summary

When running microk8s under a proxied environment, is it possible to apply HTTP proxy configuration across all future pods managed by microk8s?

Is it possible for microk8s to reroute the traffic or apply the environment variable across all new deployments?

It seems mutating admission webhook would work for the second method.

For the first method, is there any way to achieve it?

Why is this important?

Our use case is to adopt test cases that was not written with proxy in mind to run within a proxied environment.

Are you interested in contributing to this feature?

[berkayoz]

Hey @yhaliaw, This is more of a Kubernetes question, there is not a specific/special way to do this within MicroK8s. So any solution for upstream Kubernetes should work for MicroK8s as well. But generally, you'll have to manually set your proxy environment variables in your containers. You can do so by having a single ConfigMap with your settings and passing environment variables such as HTTP_PROXY and HTTPS_PROXY to the container through this ConfigMap.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.