Investigate what needs to be done for kubeflow 1.7 update

[mathis-marcotte]

Link to epic #1632

Investigate what we will need to do for when are ready to go to kubeflow 1.7

Possible things to look at;

Manifest updates?
Rebasing?

Investigate volumes and see if we need to take that in (seems like it)

• Yes we do, that is the volumes table that we display. We will just combine notebooks and volumes like we do normally.

Investigate the differences / ask if they plan on deprecating one of the centraldashboards. It would be nice to be all on angular and it does seem like they are moving in the direction of being consistent with angular

Look into deprecating jupyter-apis if the hero pr saves us from continuously updating the go code

---

We want to wait for the performance issue to be possibly fixed, however we as devs can get a head start on trying things out in the much smaller dev cluster, which would include rebasing / shifting our manifests to look upstream while using the python backend.

Overall Plans

• Fork and begin the rebase

---

Tasks for this sprint to be completed

• Investigate drift between our fork and upstream
• Create manageable tickets for breaking down of rebasing (and update the epic with findings)
• KF 1.7: Investigate new features in 1.7  #1637

[mathis-marcotte]

Completed by filling out the epic for kubeflow 1.7