Research into 1.3 Upgrade

[wg102]

This ticket is to track time about the research on this Epic #530

I will be reading into the 'how to upgrade to 1.3' and which systems it affects, expected issues etc.
The information will be independant of our own repo. By this I mean that since we have our own forks, additional work will be needed for rebasing, but it should help guide us in the process nonetheless, and possibly give and idea for the order in which to tackle all the items mentionned in the epic.

I am uncertain yet if the epic will host all additional issues for the actual tasks, or it will be in another file. Will update as more information becomes known.

Relates to https://github.com/StatCan/daaas/issues/824 as well. Any information about image update shall be added to that repo.

[wg102]

I have read a few sites/posts on how to upgrade or install the 1.3 kubeflow.
Many were not usefull. Here is the list of the ones that were.

• https://github.com/kubeflow/manifests/tree/v1.3.1
• https://www.kubeflow.org/docs/releases/kubeflow-1.3/ possibly not up to date...
• https://v1-3-branch.kubeflow.org/docs/components/

The idea is simple, start with a component, go to the next.
Some of the features would be for the Cloud team to take care.
Except istio, which we will be doing together.

For the rest, we will need to upgrade the repos. and refactor our jupyter-api to be inside kubeflow repo.
kubeflow (central dashboard + jupyter-api/crud-web-app)
pipelines - for i18n to be in the features
Katib - no need to rebase just upgrade the image

Following these information I will be editing the Epic and creating 3 issues. one for kubeflow(general), one kubeflow(crud-web-apps) and one for the pipelines. And in each of these, try to put as much detail on the work to get them rebased and upgraded. Those tickets, or their childrens if it's too big, will be the actual work done for 1.3 (in addition to any that will need to be create for istio or the deployment modification)
and also any controller we have...