Add new module to get available upgrade versions for an AKS cluster #405
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Get the upgrade versions available for a managed Azure Container Service (AKS) instance.
Essentially it has similar information in its output as command
az aks get-upgrades
.Fixes #377
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION
When you upgrade an AKS cluster, Kubernetes minor versions cannot be skipped. For example, upgrades between 1.12.x -> 1.13.x or 1.13.x -> 1.14.x are allowed, however 1.12.x -> 1.14.x is not. So you can not simply take the latest available version for new AKS instance. And that is why we need
az aks get-upgrades
command, which gets cluster name and its resource group as parameters.This is a separate module (and not part of an existing one) because it is separate both in Azure SDK and az cli tool. So it would be wise to follow the same approach here, taking into account it generates the same information in its output.
Example: