[EPIC] Kubeflow v1.2 upgrade

[saffaalvi]

Rebasing StatCan/kubeflow repository to catch up to changes made for kubeflow/kubeflow v1.2

Involves catching up two components:

• central dashboard
• jupyter-apis

End goal: everything should be under the StatCan/kubeflow repository, APIs have to be compatible, then push new features upstream

Central Dashboard

• Create a list of new features and changes made upstream until the v1.2 release. Compare centraldashboard changes up until v1.2 kubeflow#33

• Create a list of new features we’ve implemented so far. Divide into what we want to push upstream and don’t. Compare centraldashboard changes up until v1.2 kubeflow#33

• Rebase (Kubeflow v1.2 Rebasing kubeflow#34)

  • Pulling all of kubeflow/kubeflow (upstream) changes into a feature branch (is the feature branch based off of master or stc-master? -> stc-master)

  • Resolving conflicts and preserving our feature changes

  • Merge feature branch into stc-master

  • Update our 'master' branch to be in sync with upstream master (?)

• These issues need to be resolved before we can push upstream:

  • Centraldashboard links from configmap: Centraldashboard links from configmap  kubeflow#40

  • Adding i18n translations to new configmap usage: Adding i18n translations to new configmap usage kubeflow#41

  • Not sure we need this change anymore - Manage multiple profiles in central dashboard: Profile owner can only manage one profile in UI kubeflow#7 and feat(centraldashboard): Manage multiple profiles kubeflow#24

  • We also had a security update that upstream hasn't fixed yet. Something to keep in mind when we push features upstream. StatCan/kubeflow@3011617
    We changed the following for security vulnerabilities:
    coreAPI: k8s.Core_v1Api; to k8s.CoreV1Api;
customObjectsAPI: k8s.Custom_objectsApi; to k8s.CustomObjectsApi;

Jupyter Web App

• Create a list of new features and changes made upstream until the v1.2 release.
  kubeflow v1.1/1.2 upstream changes to jupyter-apis component jupyter-apis#42

• Create a list of new features we’ve implemented so far. Divide into what we want to push upstream and don’t. Compare jupyter-api changes up until v1.2 kubeflow#38

• The following was a list of tasks to complete to push our features upstream. After trying to merge jupyter-apis into StatCan/kubeflow (master branch), it was discussed that it might be easier to start manually adding in our new features to keep a cleaner and more understandable history as well as easier tracking for the features.
  The issue of pushing our features upstream has been made into a new EPIC and will no longer be tracked here.

  • Update our Golang backend to their Python backend.

  • Rebase - Move jupyter-apis (frontend) into StatCan/kubeflow jupyter-web-app kubeflow#44

    • Changes will already have been pulled in from when we rebased central dashboard

    • Implement crud-web-apps

    • Resolving conflicts and preserving our feature changes

  • Pushing features upstream

    • Making sure our features do not touch the backend...how will we push this Golang backend upstream?

[saffaalvi]

Closing this EPIC since the rebase to v1.2 is completed.

Pushing features upstream is now being tracked here: StatCan/kubeflow#45