Skip to content

Fix GKE node version selection logic#185

Closed
44past4 wants to merge 0 commit into
AI-Hypercomputer:mainfrom
44past4:main
Closed

Fix GKE node version selection logic#185
44past4 wants to merge 0 commit into
AI-Hypercomputer:mainfrom
44past4:main

Conversation

@44past4
Copy link
Copy Markdown
Contributor

@44past4 44past4 commented Sep 17, 2024

Fixes / Features

  • Fixes problem with GKE nodes version selection if the current GKE cluster version is no longer a valid GKE rapid version.

Testing / Documentation

Tested manually

  • [ y/n ] Tests pass
  • [ y/n ] Appropriate changes to documentation are included in the PR

@44past4 44past4 requested a review from Obliviour as a code owner September 17, 2024 09:14
Copy link
Copy Markdown
Collaborator

@Obliviour Obliviour left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Is it possible that the rapid release will not have a release of the same major version or lower? The current default rapid release version is 1.31 and it is currently and has support for versions old as 1.27x. 1.27x was introduced in May 2023. So I am guessimating that a major version will be in the rapid release for 1.5 years. If a user doesn't upgrade their cluster for that long then, this logic may break again.

@Obliviour
Copy link
Copy Markdown
Collaborator

@44past4 I gave you permissions to the project, I believe folks will not run the Build test properly due to permissions, do you mind moving this to a branch based PR?

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