Catégorie : Kubernetes (Page 10 of 37)

Hi!

Your AKS workloads may not need to run continuously, for example a development cluster that has node pools running specific workloads. To optimize your costs, you can completely turn off (stop) your node pools in your AKS cluster, allowing you to save on compute costs.

Stop an AKS Node Pool:

az aks nodepool stop --nodepool-name testnodepool --resource-group myResourceGroup --cluster-name myAKSCluster

Start an AKS Node Pool:

az aks nodepool start --nodepool-name testnodepool --resource-group myResourceGroup --cluster-name myAKSCluster

Maxime.

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.

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.