Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Document how you upgrade Kubeflow e.g. from 0.1. to 0.2 #57

Closed
jlewi opened this issue Jun 20, 2018 · 1 comment
Closed

Document how you upgrade Kubeflow e.g. from 0.1. to 0.2 #57

jlewi opened this issue Jun 20, 2018 · 1 comment
Assignees
@jlewi
Labels
area/docs priority/p1 sprint/2018-06-25-to-07-06

Comments

@jlewi
Copy link
Contributor

jlewi commented Jun 20, 2018

We should add some docs on how to upgrade between different versions; even if that means telling people to delete everything and recreate it from scratch since we don't have an upgrade path right now.
@jlewi jlewi mentioned this issue Jun 21, 2018
Closed
@jlewi
Copy link
Contributor Author

jlewi commented Jun 21, 2018

Here are some issues to consider

  • As with Invalid value: "v1alpha2": field is immutable kubeflow#1029 there are certain resources (like CRD definitions) that need to be explicitly deleted before users can deploy the new one.

    • Do we list individual components to delete? Do we suggest users delete the entire namespace?
      • Deleting the entire namespace seems bad because it could disrupt Jupyter work and certain resources like secrets that aren't checked in as part of the app could need to be recreated manually

  • How should users upgrade ksonnet components?

    • Do we just tell users to update the vendor directory but leave the generated components and parameters alone?
    • Do we tell users to regenerate their application like we do for dev.kubeflow.org

@jlewi jlewi self-assigned this Jun 22, 2018
jlewi added a commit to jlewi/kubeflow that referenced this issue Jun 29, 2018
@jlewi
Create a script to update a ksonnet app to the latest Kubeflow package
775495d 
* Related to: kubeflow/website#57
* Based on the script in ksonnet/ksonnet#237
This was referenced Jun 29, 2018
Merged
Merged
jlewi added a commit to jlewi/kubeflow that referenced this issue Jun 29, 2018
@jlewi
Create a script to update a ksonnet app to the latest Kubeflow package
0257c79 
* The script removes the existing registry named kubeflow and any packages
  installed from that registry
* It then readds Kubeflow using the supplied URL and reinstalls any packages.
* Related to: kubeflow/website#57
* Based on the script in ksonnet/ksonnet#237
k8s-ci-robot pushed a commit to kubeflow/kubeflow that referenced this issue Jul 10, 2018
@jlewi @k8s-ci-robot
Create a script to update a ksonnet app to the latest Kubeflow package (
bf1c2f0 
#1100)

* Create a script to update a ksonnet app to the latest Kubeflow package

* The script removes the existing registry named kubeflow and any packages
  installed from that registry
* It then readds Kubeflow using the supplied URL and reinstalls any packages.
* Related to: kubeflow/website#57
* Based on the script in ksonnet/ksonnet#237

* * Only delete the registry entry in app.yaml corresponding to
  the registry being upgraded; and only delete the packages in that
  registry.
saffaalvi pushed a commit to StatCan/kubeflow that referenced this issue Feb 11, 2021
@jlewi @k8s-ci-robot
Create a script to update a ksonnet app to the latest Kubeflow package (
6edfed3 
kubeflow#1100)

* Create a script to update a ksonnet app to the latest Kubeflow package

* The script removes the existing registry named kubeflow and any packages
  installed from that registry
* It then readds Kubeflow using the supplied URL and reinstalls any packages.
* Related to: kubeflow/website#57
* Based on the script in ksonnet/ksonnet#237

* * Only delete the registry entry in app.yaml corresponding to
  the registry being upgraded; and only delete the packages in that
  registry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jlewi jlewi

Labels
area/docs priority/p1 sprint/2018-06-25-to-07-06
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jlewi