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

Support Kubernetes v1.27 - v1.29 #2256

Closed
Tracked by #2255
andreyvelich opened this issue Jan 29, 2024 · 5 comments · Fixed by #2308
Closed
Tracked by #2255

Support Kubernetes v1.27 - v1.29 #2256

andreyvelich opened this issue Jan 29, 2024 · 5 comments · Fixed by #2308
Assignees

Comments

@andreyvelich
Copy link
Member

As part of Katib 0.17 release we need to support Kubernetes v1.27 - v1.29 versions.

Currently, we validate Katib for Kubernetes v1.25 - v1.27 in our integration tests.
We should drop support for v1.25 and v1.26 and add support for v1.28 and v1.29.

Let's identify the required changes in this issue.

cc @kubeflow/wg-training-leads @tenzen-y @kubeflow/release-team

@Ayush9026
Copy link

/assign @Ayush9026 i will solve this issue sir.

@tenzen-y
Copy link
Member

tenzen-y commented Mar 2, 2024

/assign @Ayush9026 i will solve this issue sir.

@Ayush9026 Are you still working on this? If so, could you 2 separate PRs so that we can revert the dedicated commit once we face the dependency issues?

The first one: Drop v1.25 and Intriduce v1.28
The second one: Drop: v1.26 and Introduce v1.29.

@Ayush9026
Copy link

Yes @tenzen-y sir i am working on it thanks for telling i will create two separate PR as you tell.

@andreyvelich
Copy link
Member Author

@Ayush9026 Please can you let us know what is the status of this issue ?
We need to create PR this week since we are going to cut the Katib release in 2 weeks.

@tenzen-y
Copy link
Member

This is the significant blocker for our next release. So, I take this issue.
/unassign @Ayush9026
/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.

3 participants