-
Notifications
You must be signed in to change notification settings - Fork 4
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
kubeflow v1.1/1.2 upstream changes to jupyter-apis component #42
Comments
Kubeflow v1.1Overall, it has been difficult to find a comprehensive list of all the new features Kubeflow v1.1 has introduced. The changes mentioned below are what I've noticed from v1.1 branch commits in the This blog post talks more in detail about the changes in v1.1. I think the Notebooks Table
Volume (Resource Form)
|
Kubeflow v1.2After Kubeflow v1.1 was released, the major change was a new directory for web apps that shared common code (includes Jupyter, Tensorboard, and Volumes UI). There are still commits being made to both the old There is more information for what v1.2 will have in their release description https://github.com/kubeflow/kfctl/releases/tag/v1.2-rc.0 and this roadmap issue kubeflow/kubeflow#5224. Some features mentioned below were found from the following PRs: Old jupyter-web-app Component
New Directory for Common Web Apps (crud-web-apps)
|
MiniKFWhen running MiniKF, these are some changes I've seen that I'm not sure have been/will be implemented in v1.1 or v1.2: Notebooks Table
Volumes TableWhile we have the volumes table underneath the notebook servers table, the new kubeflow version in MiniKF has it as an extra menu option in the left sidebar. This table has additional features such as:
|
@sylus @zachomedia @brendangadd @blairdrummond ^ What is/isn't in 1.2 for the jupyter web app is hella confusing, but Saffa's got a solid summary if anyone needs a good place to start for figuring it out. |
v1.1 - Manifest TagsCompared using the v1.1.0 release commits.
FEB 25 - [CentralDashboard][Testing] End-to-end testing added
|
v1.2 - Manifest Tags
SEP 29 - Refactor the JWA backend to utilize common code
|
The manifest released the v1.2.0 tag on November 20th. As it currently was on November 28th, The back end part – notebook-controller - was updated with the image kubeflow/kubeflow@6eb007d to refactor the JWA backend to utilize common code. On Nov 4th, an auto PR updated the notebook-controller tag to the one mentioned above, vmaster-g6eb007d0 (kubeflow/manifests@0f673cf). In the release, the latest there was a PR to update some of the images in manifest two weeks ago, aka nov 16th kubeflow/manifests#1645, but they updated with rather old tags. (See details for V1.2 in the comment above)
The front-end crud web app changes have not yet been implemented in the V1.2 release commits since we couldn’t find the commit tag anywhere in the manifest. The latest tag is vmaster-g845af298 which has the commit of AUG 7 - Fix #5111: Trim whitespace from custom images (kubeflow/kubeflow@845af29) To summarize, v1.2 has the commit that contained the crud-web-app backend using common code, however maybe because it is still being worked on, the frontend for crud web apps has not been updated in the manifest. Things to keep an eye on:
|
Summary of upstream changes that we may have to integrate into the
jupyter-apis
component when upgrading to v1.1/1.2.The text was updated successfully, but these errors were encountered: