-
Notifications
You must be signed in to change notification settings - Fork 12
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: define upgrade path to kf 1.4 #1225
Comments
Kubeflow v1.4.0 Release NotesThis is a checklist of all the items we need to check before the upgrade can proceed. Just take note of whether we need to do any work to upgrade or if we can simply rebase. Web apps:(Assigned to @bryanpaget)
✅ We will have to upgrade to Angular 12 since everything else depends on it. Internationalization progress(Assigned to @wg102)
Central Dashboard:(Assigned to @bryanpaget) Compare to our code, we have to keep our branding and links specific to AAW/DAaaS.
Jupyter web app(Assigned to @wg102) This is where we have the most customization and we even use a different backend.
Notebooks(Assigned to @bryanpaget)
TensorBoards(Assigned to @wg102)
PodDefaults(Assigned to @bryanpaget)
Other improvements(Assigned to @wg102)
|
According to the Kubeflow 1.4.1 release notes, https://www.kubeflow.org/docs/releases/kubeflow-1.4/, we'll need to use Kubeflow Pipelines 1.7.0 with Kubeflow 1.4.1. |
TODO: Once we go throught the kubeflow repo changes, we will need to compare the manifest. |
The details have been added to the epic |
Epic: #1203
Placeholder ticket to start the kubeflow 1.4 planning and task creation
The text was updated successfully, but these errors were encountered: