Hi!

The following labels are planned for deprecation with the release of Kubernetes v1.24. Customers should change any label references to the recommended substitute.

Label	Recommended substitute	Maintainer
failure-domain.beta.kubernetes.io/region	topology.kubernetes.io/region	Kubernetes
failure-domain.beta.kubernetes.io/zone	topology.kubernetes.io/zone	Kubernetes
beta.kubernetes.io/arch	kubernetes.io/arch	Kubernetes
beta.kubernetes.io/instance-type	node.kubernetes.io/instance-type	Kubernetes
beta.kubernetes.io/os	kubernetes.io/os	Kubernetes
node-role.kubernetes.io/agent*	kubernetes.azure.com/role=agent	Azure Kubernetes Service
kubernetes.io/role*	kubernetes.azure.com/role=agent	Azure Kubernetes Service
Agentpool*	kubernetes.azure.com/agentpool	Azure Kubernetes Service
Storageprofile*	kubernetes.azure.com/storageprofile	Azure Kubernetes Service
Storagetier*	kubernetes.azure.com/storagetier	Azure Kubernetes Service
Accelerator*	kubernetes.azure.com/accelerator	Azure Kubernetes Service

Maxime.

Hi!

In this article, I will share with you some information related to the Azure release tracker:

AKS releases weekly rounds of fixes and feature and component updates that affect all clusters and customers. However, these releases can take up to two weeks to roll out to all regions from the initial time of shipping due to Azure Safe Deployment Practices (SDP). It is important for customers to know when a particular AKS release is hitting their region, and the AKS release tracker provides these details in real time by versions and regions.

Use the AKS release tracker to: 

• See AKS deployments real time, every week by region
• See the flow of deployment (SDP) between one region to the next
• Get links from the page to the current and past release notes 

To view the release tracker, visit the AKS release status webpage.

Maxime.

Hi!

In this article, I will show you how you can remove the Defender for Containers profile from an existing AKS Cluster.

az login az account set --subscription <subscription-id> az aks update --disable-defender --resource-group <your-resource-group> --name <your-cluster-name> 

To verify that the profile was successfully removed, run the following command:

kubectl get pods -n azuredefender

Maxime.