Catégorie : Azure

AKS | HTTP Proxy Support


Azure Kubernetes Service (AKS) clusters, regardless of whether they’re deployed in a managed or custom virtual network, require specific outbound dependencies to operate effectively. Previously, in environments where internet access had to be routed through HTTP proxies, this presented a challenge. Nodes lacked the means to bootstrap the essential configuration, environment variables, and certificates needed to connect to internet services.

With this newly introduced feature, AKS clusters now support HTTP proxies. This provides a user-friendly interface for cluster operators to manage network traffic required by AKS in environments dependent on proxies, ensuring a secure and smooth operation.

Example of Json HTTP Proxy Config File:

  "httpProxy": "string",
  "httpsProxy": "string",
  "noProxy": [
  "trustedCa": "string"

Create a new AKS cluster with HTTP proxy configured on the nodes:

az aks create -n $clusterName -g $resourceGroup --http-proxy-config aks-proxy-config.json

Update an existing HTTP proxy:

az aks update -n $clusterName -g $resourceGroup --http-proxy-config aks-proxy-config-2.json

Note: ods must be rotated for the apps to pick it up. For components under kubernetes, like containerd and the node itself, this won’t take effect until a node image upgrade is performed.

The following scenarios are not supported:

  1. Varied proxy configurations for each node pool
  2. User/password authentication
  3. Custom Certificate Authorities (CAs) for API server communication
  4. Windows-based clusters
  5. Node pools utilizing Virtual Machine Availability Sets (VMAS)
  6. Employing ‘*’ as a wildcard appended to a domain suffix for noProxy

Additionally, it’s important to note that by default, both httpProxy and httpsProxy, as well as trustedCa, are unset.



Azure Resource Graph Policy Exceptions 


I’m excited to share that you can now harness the power of Azure Resource Graph to effortlessly retrieve all policy exceptions. This is made even more seamless with the introduction of the new field: microsoft.authorization/policyexemptions.

Example: Extract all the policies which expire within 90 days

PolicyResources | where type == 'microsoft.authorization/policyexemptions' | extend expiresOnC = todatetime(properties.expiresOn) | where isnotnull(expiresOnC) | where expiresOnC >= now() and expiresOnC < now(+90d) | project name, expiresOnC

Example: All the policies exceptions per assignment

PolicyResources | where type == 'microsoft.authorization/policyexemptions' | summarize count() by tostring(properties.policyAssignmentId)


AKS | Release Tracker


AKS releases weekly updates, including fixes, features, and component enhancements, affecting all clusters and customers. However, due to Azure Safe Deployment Practices (SDP), it may take up to two weeks for these updates to be fully deployed across all regions from the initial shipping date.

It is imperative for customers to stay informed about when a particular AKS release will reach their region, and the AKS release tracker provides real-time information sorted by versions and regions. This tool empowers customers to monitor specific component updates included in an AKS version release, such as fixes applied to a core add-on.