-
Notifications
You must be signed in to change notification settings - Fork 314
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
[Feature] Cluster automatic upgrade for K8s versions #1303
Comments
Hi @jluk , Thanks, |
I came across this issue and saw the announcement in Jan of 2019 (https://azure.microsoft.com/en-us/updates/aks-cluster-auto-upgrade/) that this is being worked on, but the feature isn't even in preview yet, correct? |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
activity |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
Unstale! |
Hi @jluk any update on this issue please ? |
Now In Preview : https://docs.microsoft.com/en-us/azure/aks/upgrade-cluster#set-auto-upgrade-channel-preview |
When can we expect this in General availability (GA) ? |
it seems the current preview version doesn't support setting the timeslot to enable the upgrade? like, I only want to upgrade during weekend. |
Is there a way to verify to which upgrade channel the cluster has been set? |
That seems to be covered by this feature: https://docs.microsoft.com/en-us/azure/aks/planned-maintenance |
The document page here doesn't have the "preview" keyword in the title.. does it mean this is GA? https://docs.microsoft.com/en-us/azure/aks/upgrade-cluster#set-auto-upgrade-channel |
is Auto-Upgrade Channel for AKS is GA? |
Adding to the last few comments, I'd love to know when this is expected to be GA if it isn't already. |
@wangyira |
Hey everyone, We are planning to GA this feature very soon. It should be rolling out in the next 2-3 weeks. |
GA |
What happened: Today, cluster upgrades require manual intervention and explicit setting of the major.minor.patch versions for Kubernetes. This process must be done at semi-regular intervals to stay within the supported window of Kubernetes versions and would benefit from reduced friction.
What you expected to happen: User is able to opt-in to using automatic upgrades for a given AKS clusterl. The cluster set for auto-upgrade would be upgraded with a newer Kubernetes version in-line with a setting defined by the user which dictates frequency and what the target version should be.
The text was updated successfully, but these errors were encountered: