[Chore] Bump AKS and EKS versions explicitly #12
Merged
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.
This MR does the following:
Explicitly upgrades K8s versions for EKS and AKS
AKS as of today is at 1.27.3 (validate by running az aks get-versions --location westus --output table ). Note AKS needs the patch version i.e X.Y.Z version set
EKS as of today is at 1.27 see here
GKE is on a "release channel", our default is "regular" which as of today gives 1.27. See here
We will move to 1.28 next month when its available on AKS since the other 2 CSPs have it.
What to test to validate.
kubectl version
. The version reported forserver
is what was provisioned.