From ea490a2008da035c95354439a71bf900bf0921a3 Mon Sep 17 00:00:00 2001 From: Chase Wilson <31453523+chasewilson@users.noreply.github.com> Date: Mon, 20 Jan 2025 10:44:43 -0700 Subject: [PATCH] Update CHANGELOG.md --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 70432dad..70ce1688 100755 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -73,7 +73,7 @@ https://azure.microsoft.com/updates/azure-basic-load-balancer-will-be-retired-on * [GitHub Copilot](https://azure.microsoft.com/products/github/Copilot) for Azure now supports [AKS commands](https://learn.microsoft.com/azure/aks/aks-extension-ghcopilot-plugins). * You can now skip one release [while upgrading Azure Service Mesh](https://learn.microsoft.com/azure/aks/istio-upgrade) as long as the destination release is a supported revision - for example, asm-1-21 can upgrade directly to asm-1-23. * You can now fine-tune supported models on KAITO version [0.3.1](https://github.com/Azure/kaito/releases/tag/v0.3.1) with the AI toolchain operator add-on on your AKS cluster. - * Advanced Container Networking Services (ACNS) is now Generally Availabe. To earn more please see the [ACNS Documentation](https://learn.microsoft.com/azure/aks/advanced-container-networking-services-overview?tabs=cilium). + * Advanced Container Networking Services (ACNS) is now Generally Available. To earn more please see the [ACNS Documentation](https://learn.microsoft.com/azure/aks/advanced-container-networking-services-overview?tabs=cilium). * Preview features: * We've added [a new way to optimize your upgrade process drain behavior](https://learn.microsoft.com/azure/aks/upgrade-cluster?tabs=azure-cli#optimize-for-undrainable-node-behavior-preview). By default, a node drain failure causes the upgrade operation to fail, leaving the undrained nodes in a schedulable state, this behavior is called `Schedule`. Alternatively, you can select the `Cordon` behavior, which skips nodes that fail to drain by placing them in a quarantined state, labeling them `kubernetes.azure.com/upgrade-status:Quarantined` and proceeds with upgrading the remaining nodes. This ensures that all nodes are either upgraded or quarantined. This approach allows you to troubleshoot drain failures and gracefully manage the quarantined nodes.