Skip to content

Commit

Permalink
dev updates
Browse files Browse the repository at this point in the history
  • Loading branch information
allyford committed May 30, 2023
1 parent 17b094f commit 041bcd3
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,10 @@ Monitor the release status by regions at [AKS-Release-Tracker](https://releases.
* [Automated deployments](https://learn.microsoft.com/azure/aks/automated-deployments) now supports draft. Take your application and automatically create dockerfiles, kubernetes manifests, and github actions to deploy it onto your AKS cluster with ease.

* Behavior Changes
* Customers may not upgrade to v1.25 and above if PSP is enabled, an error will occur if attempted.
* PodSecurityPolicy is removed in AKS clusters v1.25 and higher. Customers may not upgrade to v1.25 and above if PSP is enabled, an error will occur if attempted. PSP needs to be disabled before upgrading.
* Added hint to help guide users to install kubelogin if not already in their PATH.
* Updated error handling for VMs failing with the same error code (50,51,52).
* large-cluster-overrides.yaml is not disabled for free tier clusters in subscriptions included in the file.
* Added configmap hash to cilium agent and operator annotations. The configmap hash will appear in the k8s manifests for [cilium-operator and cilium-agent](https://learn.microsoft.com/azure/aks/azure-cni-powered-by-cilium).
* Improved error messages and public documentation for errors [50](https://learn.microsoft.com/troubleshoot/azure/azure-kubernetes/error-code-outboundconnfailvmextensionerror), [51](https://learn.microsoft.com/troubleshoot/azure/azure-kubernetes/error-code-k8sapiserverconnfailvmextensionerror), and [52](https://learn.microsoft.com/troubleshoot/azure/azure-kubernetes/error-code-k8sapiserverdnslookupfailvmextensionerror). Now when customers encounter these errors, they should be able to resolve them by accessing the appropriate section in our troubleshooting documentation.
* Web Application Routing now supports configuration through the Azure portal.

* Bug Fixes
Expand Down

0 comments on commit 041bcd3

Please sign in to comment.