[Epic] K8s 1.22 / Kubeflow 1.6

[Collinbrown95]

Description

Upgrade K8s 1.22 then upgrade Kubeflow 1.6
Closes #681 #1094

TODO

K8s

• Reach out to CNS and get date for upgrading aaw-dev cluster from 1.21.9 to 1.22.x
• add back useruc and userpb node pools @Collinbrown95

Kubeflow 1.6

• Verify that we don't need to immediately rebase front-end (i.e. can have front-end broken while other dev components are working) @wg102 : The code is changed a lot, including CRDs, so it's very hard to guess.
• Test mandatory components (TODO add list with what these components are) and make sure that 1.6 works correctly. In particular, for each component:
  • Update manifests from 1.4 to 1.6
  • apply to aaw-dev cluster
  • create any AAW-specific kustomizations
  • document any AAW-specific kustomizations we made

Manifest

This epic list the table and all isseus related to it

• Check this box once they are all *Core components are merged in
• Test and fix KF 1.6 core components #1352

• Important: the only components we 100% need working for dev environment is central dashboard and crud-webapps

Kubeflow Central Dashboard

• Fix the broken localization in 1.4 dev #1340
• Rebase Kubeflow onto v1.6.0 #1341
• Ugrade 1.6 Fix CentralDashboard Vulnerabilities
  Note: Rebase vs merge?
• List the broken features/one needed work and spread the tasks around

Crud-Web-Apps

A initial table for 1.4 was done in this issue: #1242

• Investigate how to deploy angular i18n jupyter-apis#126
• Deploy Angular i18n jupyter-apis#133
• Upgrade 1.6: Fix Backend jupyter-apis#125
• "Rebase" for 1.6 Crud-web-apps #1342
• Features to recode [Epic] Upgrade JWA 1.6 Commits to Redo jupyter-apis#131
• 1.6 update translation files jupyter-apis#160
• 1.6 missing storage classes endpoint jupyter-apis#159

Pipelines:

This one would be lower priority than the other two above

• Check which version to use
• Rebase Pipeline version 2.0.0-alpha.3 #1343
• Rebase or merge (to confirm) to that version
• [EPIC] Pipeline version 2.0.0-alpha.3 testing #1349

Next Steps

• Are there any upstream components that we can stop supporting (e.g. Katib, Kubeflow pipelines, etc.)? Idea is to reduce maintenance burden and stop supporting components that no one is using. TODO : discuss with whole team later

[bryanpaget]

[Epic] Kubeflow Manifests 1.6 Upgrade #1336

[wg102]

Taking a note for the next step and to mention it at standup, other than this, the epic is done and since Kubeflow 1.6 is in Prod, it is time to close it.