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

[Chore] Bump AKS and EKS versions explicitly #12

Merged
merged 1 commit into from
Sep 27, 2023

Conversation

evberrypi
Copy link
Collaborator

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.

  1. Provision a new cluster
  2. Run kubectl version. The version reported for server is what was provisioned.
  • AKS will be at 1.27.3. GKE and AKS must be at 1.27.X (where X does not matter)

@evberrypi evberrypi merged commit 23dfca5 into NVIDIA:main Sep 27, 2023
@evberrypi evberrypi deleted the elacey/2309-k8supgrade branch September 27, 2023 01:51
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.

2 participants