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

Release 2023-10-01 #3931

Merged
merged 8 commits into from
Oct 6, 2023
Merged

Release 2023-10-01 #3931

merged 8 commits into from
Oct 6, 2023

Conversation

stl327
Copy link
Contributor

@stl327 stl327 commented Oct 2, 2023

No description provided.

CHANGELOG.md Outdated

* Features
* [H100 GPUs (accelerated compute instances)](https://learn.microsoft.com/en-us/azure/virtual-machines/nd-h100-v5-series) are now supported on AKS, with two current SKU offerings: Standard_ND96isr_v5 and Standard_ND96is_v5.
* Support for IP address changes for [Azure Blob NFS mounts](https://github.com/Azure/AZNFS-mount) on AKS 1.27+.
Copy link
Member

Choose a reason for hiding this comment

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

Azure docs link. @andyzhangx @AllenWen-at-Azure could you add this to our docs?

This comment was marked as outdated.

Copy link
Contributor

Choose a reason for hiding this comment

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

CHANGELOG.md Outdated

* Behavioral Changes
* The pod CPU request from [ama-metrics](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/prometheus-metrics-overview) daemonsets will be reduced in Windows from 500m to 150m and in Linux from 75m to 50m.
* If your VM SKU does not support ephemeral or Premium SSD OS disks, AKS will now use Standard SSD as the default OS disk type as compared to Standard HDD previously.
Copy link
Member

Choose a reason for hiding this comment

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

This was already in the previous notes?

CHANGELOG.md Show resolved Hide resolved
### Announcements

* No new clusters can be created with [Azure AD Integration (legacy)](https://learn.microsoft.com/azure/aks/azure-ad-integration-cli). Existing AKS clusters with Azure Active Directory integration will keep working. All Azure AD Integration (legacy) AKS clusters will be migrated to [AKS-managed Azure AD](https://learn.microsoft.com/azure/aks/managed-azure-ad) automatically starting from 1st Dec. 2023. We recommend updating your cluster with AKS-managed Azure AD before 1 Dec 2023. This way you can manage the API server downtime during non-business hours.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I have noticed there has been no GA announcement for VPA in the AKS release notes. Maybe we could get it added to this release note as it seems to have gone to GA 27th September. https://azure.microsoft.com/en-gb/updates/ga-vertical-pod-autoscaling-addon-for-aks/

Copy link
Collaborator

Choose a reason for hiding this comment

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

Thanks for adding. I just noticed we need to remove the en-us from the URL.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Also check the other URLs as the new ones in this pr have en-us also and should be removed.

CHANGELOG.md Outdated
* If the ama-logs add-on is enabled, host port 28330 will be mounted to the ama-logs daemonset in order to facilitate syslog collection.
* To reduce vertical pod autoscaling (VPA) out of memory (OOM) errors, the vpa-recommender CPU limit will increase to 1000m, memory limit to 2000Mi, and memory request to 800Mi from 200m, 1000m, and 500Mi respectively.
* All control plane upgrades to AKS 1.26+ will enforce deprecated API usage validation. You can bypass this check and frontend pdb validation with [forceUpgrade](https://learn.microsoft.com/azure/aks/upgrade-cluster?tabs=azure-cli#stop-cluster-upgrades-automatically-on-api-breaking-changes-preview).
* The default [max surge](https://learn.microsoft.com/azure/virtual-machines/nd-h100-v5-series) value during upgrades will be changed from 1 to 10% for AKS 1.28+ on new clusters to improve upgrade latency.
Copy link
Contributor

@aritraghosh aritraghosh Oct 4, 2023

Choose a reason for hiding this comment

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

Is the link for default max surge correct?

CHANGELOG.md Outdated
* Bug Fixes
* Fix for some events during an upgrade such as "Deleting node" not appearing in kubectl get events.
* Fix for metricsDefinition operation not exposed in Azure China.
* Fix for [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/releases) condition where nodes that VPA pods are scheduled to could not be evicted.
Copy link
Member

Choose a reason for hiding this comment

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

This is the general release page, when people click this link they will go to the latest

CHANGELOG.md Outdated
### Announcements

* No new clusters can be created with [Azure AD Integration (legacy)](https://learn.microsoft.com/azure/aks/azure-ad-integration-cli). Existing AKS clusters with Azure Active Directory integration will keep working. All Azure AD Integration (legacy) AKS clusters will be migrated to [AKS-managed Azure AD](https://learn.microsoft.com/azure/aks/managed-azure-ad) automatically starting from 1st Dec. 2023. We recommend updating your cluster with AKS-managed Azure AD before 1 Dec 2023. This way you can manage the API server downtime during non-business hours.
* The [vertical pod autoscaling (VPA)](https://learn.microsoft.com/azure/aks/vertical-pod-autoscaler) add-on for AKS is now generally available.
Copy link
Member

Choose a reason for hiding this comment

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

This should be in feature

CHANGELOG.md Outdated
* To reduce vertical pod autoscaling (VPA) out of memory (OOM) errors, the vpa-recommender CPU limit will increase to 1000m, memory limit to 2000Mi, and memory request to 800Mi from 200m, 1000m, and 500Mi respectively.
* All control plane upgrades to AKS 1.26+ will enforce deprecated API usage validation. You can bypass this check and frontend pdb validation with [forceUpgrade](https://learn.microsoft.com/azure/aks/upgrade-cluster?tabs=azure-cli#stop-cluster-upgrades-automatically-on-api-breaking-changes-preview).
* The default [max surge](https://learn.microsoft.com/azure/aks/upgrade-cluster?tabs=azure-cli#customize-node-surge-upgrade) value during upgrades will be changed from 1 to 10% for AKS 1.28+ on new clusters to improve upgrade latency.
* Enabled support worklflows with update/patch access to validating and mutating webhookconfigurations, list/get access to volumeattachments, and get access to image integrity CRDs - policy, certificatestore, verifier, and store.
Copy link
Member

Choose a reason for hiding this comment

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

What is this? Also typo on workflows
This doesn't sound like a behavior change or a public piece, also image integrity announcement was already done or not?

CHANGELOG.md Outdated

* Behavioral Changes
* The pod CPU request from [ama-metrics](https://learn.microsoft.com/azure/azure-monitor/essentials/prometheus-metrics-overview) daemonsets will be reduced in Windows from 500m to 150m and in Linux from 75m to 50m.
* Public CIDRs, including those from placing the service/pod CIDR in the multicast address space, will be validated during creation by AKS to improve cluster connectivity.
Copy link
Member

Choose a reason for hiding this comment

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

Per the thread we need to improve this lingo.

AKS will now validate/block the usage of the following multicast address spaces XXXXX.

Also this needs to be added to the docs explicitly just in case. @chasewilson @phealy

CHANGELOG.md Outdated
* Public CIDRs, including those from placing the service/pod CIDR in the multicast address space, will be validated during creation by AKS to improve cluster connectivity.
* If the ama-logs add-on is enabled, host port 28330 will be mounted to the ama-logs daemonset in order to facilitate syslog collection.
* To reduce vertical pod autoscaling (VPA) out of memory (OOM) errors, the vpa-recommender CPU limit will increase to 1000m, memory limit to 2000Mi, and memory request to 800Mi from 200m, 1000m, and 500Mi respectively.
* All control plane upgrades to AKS 1.26+ will enforce deprecated API usage validation. You can bypass this check and frontend pdb validation with [forceUpgrade](https://learn.microsoft.com/azure/aks/upgrade-cluster?tabs=azure-cli#stop-cluster-upgrades-automatically-on-api-breaking-changes-preview).
Copy link
Member

Choose a reason for hiding this comment

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

This means this feature is GA and that doc needs to be updated @shashankbarsin

Is the LRB finished?

CHANGELOG.md Outdated

* Bug Fixes
* Fix for some events during an upgrade such as "Deleting node" not appearing in kubectl get events.
* Fix for metricsDefinition operation not exposed in Azure China.
Copy link
Contributor

Choose a reason for hiding this comment

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

What is this metricsDefinition operation, do we have a link to docs?

CHANGELOG.md Outdated
* AKS will now validate, and block if necessary, service CIDRs placed in [public and multicast IP address ranges](https://learn.microsoft.com/azure/virtual-network/virtual-networks-faq#what-address-ranges-can-i-use-in-my-virtual-networks).
* If the ama-logs add-on is enabled, host port 28330 will be mounted to the ama-logs daemonset in order to facilitate syslog collection.
* To reduce vertical pod autoscaling (VPA) out of memory (OOM) errors, the vpa-recommender CPU limit will increase to 1000m, memory limit to 2000Mi, and memory request to 800Mi from 200m, 1000m, and 500Mi respectively.
* All control plane upgrades to AKS 1.26+ will enforce deprecated API usage validation. You can bypass this check and frontend pdb validation with [forceUpgrade](https://learn.microsoft.com/azure/aks/upgrade-cluster?tabs=azure-cli#stop-cluster-upgrades-automatically-on-api-breaking-changes-preview).
Copy link
Contributor

Choose a reason for hiding this comment

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

This sounds like a feature, why is it the behavior chance section, and it should then be accompanied by docs and LRB approval as Jorge tagged


### Release notes

* Features
Copy link
Contributor

Choose a reason for hiding this comment

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

@stl327 add
GA of BYOK for ephemeral disk

@stl327 stl327 merged commit 80f2064 into Azure:master Oct 6, 2023
2 checks passed
stl327 added a commit that referenced this pull request Oct 6, 2023
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.

7 participants