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

Kubernetes versions for the next katib version #2155

Closed
tenzen-y opened this issue May 17, 2023 · 3 comments · Fixed by #2182
Closed

Kubernetes versions for the next katib version #2155

tenzen-y opened this issue May 17, 2023 · 3 comments · Fixed by #2182

Comments

@tenzen-y
Copy link
Member

/kind discussion

Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Currently, we support 3 K8s versions, such as v1.23, v1.24, and v1.25.

However, v1.23 has already reached EoL, and v1.24 will reach EoL on 2023-07-28.

So we can support v1.24-v1.26 or v1.25-v1.27 in the next katib release.

ref: https://kubernetes.io/releases/

cc: @kubeflow/wg-automl-leads @anencore94

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

The training operator will support the v1.25-v1.27 in the next release.

ref: kubeflow/training-operator#1803 (comment)


Love this feature? Give it a 👍 We prioritize the features with the most 👍

@andreyvelich
Copy link
Member

Thank you for creating this @tenzen-y.

I think, we agreed for these Kubernetes versions: v1.25, v1.26, v1.27 for the next Katib release during our last AutoML and Training Community Meeting.

@tenzen-y
Copy link
Member Author

Thank you for creating this @tenzen-y.

I think, we agreed for these Kubernetes versions: v1.25, v1.26, v1.27 for the next Katib release during our last AutoML and Training Community Meeting.

Thank you for letting me know :)
I agree with the supported list.

@tenzen-y
Copy link
Member Author

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants