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

AKS Supports Same-Version upgrades (Refresh) #893

Open
jnoller opened this issue Apr 1, 2019 · 0 comments

Comments

@jnoller
Copy link
Collaborator

commented Apr 1, 2019

AKS does not currently support same-version upgrades (refresh to latest underlying components).

Tracking Feature/Functionality request:

AKS should support same-version upgrades that:

  • Refreshes, in-place all applicable component versions (Kubernetes, proxy, DNS, Azure Monitoring, Docker/Moby runtime, etc) to the latest release compatible with that Kubernetes release.
  • Preserves all data, including Node labels, annotations, etc
  • AKS should have a version file / API /etc that exposes the versions of all integrated components in a human/machine readable format

Currently, same-version upgrades (eg. 1.12.6 to 1.12.6) are blocked unless the cluster is in a Failed State (as noted by the Azure Portal or Azure CLI). In this scenario, AKS allows the same version upgrade through to assist in repairing a cluster impacted by transient issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.