The HTTP proxy
feature adds HTTP proxy support to AKS clusters, exposing a straightforward
interface that you can use to secure AKS-required network traffic in
proxy-dependent environments. With this feature, both AKS nodes and pods are
configured to use the HTTP proxy. The feature also enables installation of a
trusted certificate authority onto the nodes as part of bootstrapping a
cluster.
HTTP Proxy can now be enabled on an existing cluster
by updating the cluster to add an HTTP Proxy configuration. AKS will automatically reimage all node pools in the
cluster when you update the proxy configuration on your cluster using the az aks update command. You can use
Pod Disruption Budgets (PDBs) to safeguard disruption to critical pods during
reimage. Learn more.