Kubeflow 1.7

[yannick-roeder]

We would love to run Kubeflow 1.7 on Openshift. Are there any plans to update this repository for Kubeflow 1.7 in the near future?

This would also resolve compatibility issues with Openshift 4.10+ (#112).

[utsumi-fj]

I want to know the same thing. I would also like to know the release cycle.
The plan was changed from kubeflow#2312 (comment) ?

[utsumi-fj]

@VaishnaviHire @LaVLaS
Do you know the release schedule for 1.7 ?

[LaVLaS]

We put our support for Kubeflow releases, specifically KF 1.7, on hold due to internal resourcing issues and focusing of support for specific KF components used in ODH. While we skipped the KF 1.7 release, we do plan to provide manifests for the KF 1.8 release (kubeflow#2449 (comment)).

At this time, we have not discussed adding manifests for KF 1.7 on OpenShift but I will leave this issue open as we are having internal discussions on the possibility of extending our existing KF support to the entire KF stack running on OpenShift

CC @jeremyeder

[utsumi-fj]

@LaVLaS Thanks so much for your reply. I got it.

but I will leave this issue open as we are having internal discussions on the possibility of extending our existing KF support to the entire KF stack running on OpenShift

Does extending KF support to the entire KF stack running on OpenShift mentioned above mean extending current limited functionality such as #114 ?

[LaVLaS]

For the previous KF releases where we did provide manifests for deploying on OCP, there were two types levels of effort

1. Ensure that there were no major blockers in the KF release that would prevent it from deploying on OpenShift
2. Provide proof of concept work for integration downstream projects (UBI base images, Red Hat Service Mesh, ODH Jupyter notebooks, ...)

Does extending KF support to the entire KF stack running on OpenShift mentioned above mean extending current limited functionality such as #114 ?

I can't provide a answer to #114 without setting aside time to debug the differences. The KF 1.6 on OpenShift release was extremely limited in the amount of time we could devote to testing the release. While we don't have an increase in the resources providing KF 1.7 release testing on OCP our focus is solely on ensuring the vanilla KF releasesworks on OpenShift so any difference in functionality is a bug that should be filed here to see if it is a fix on OpenShift or upstream KF