Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anbubin/4 2 24 release notes #4192

Merged
merged 34 commits into from
Apr 11, 2024

Conversation

abubinski
Copy link
Contributor

Release notes for 3-31-24 release.

@kaarthis
Copy link
Contributor

kaarthis commented Apr 4, 2024

Please add this -
Starting 1.30 kubernetes version and 1.27 LTS versions the beta apis will be disabled by default. There will be an option provided to enable explicitly beta apis closer to the 1.30 release.
If you use any programming/ scripting logic to list and select minor version before creating clusters - please ensure you update the logic to exclude LTS-only versions to avoid any breaks. Otherwise, if LTS is your path forward please first opt into premium tier and LTS support plan as mentioned in Long-term support for Azure Kubernetes Service (AKS) - Azure Kubernetes Service | Microsoft before the create operation.
Calico can now be disabled for an AKS cluster through the update operation more info here -
https://learn.microsoft.com/en-us/azure/aks/use-network-policies#uninstall-azure-network-policy-manager-or-calico-preview

Copy link

@AdamSharif-MSFT AdamSharif-MSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi all, looking at the draft release notes I noticed that we say here "Support upgrade version skew policy between core node and control plane components from n-1 to n-3 per" - should this read instead "Support upgrade version skew policy between core node and control plane components from n-2 to n-3 per"?
Also does that mean that going forward we will support 4 stable versions from now on, that the n-3 will include a beta version too (if available) - if so I wonder if that's worthy of a separate call-out?

abubinski and others added 6 commits April 10, 2024 17:38
Co-authored-by: Shashank Barsin <[email protected]>
Co-authored-by: Shashank Barsin <[email protected]>
Co-authored-by: Shashank Barsin <[email protected]>
Co-authored-by: Shashank Barsin <[email protected]>
Copy link
Contributor

@sabbour sabbour left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM once Shashank's comments are addressed.

@abubinski abubinski merged commit 12538d9 into Azure:master Apr 11, 2024
2 checks passed
@abubinski abubinski deleted the anbubin/4-2-24-release-notes branch April 11, 2024 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants