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

design upgrade procedure from previous istio (charmed or not) to this solution #7

Open
ca-scribner opened this issue Jul 25, 2024 · 2 comments
Open

design upgrade procedure from previous istio (charmed or not) to this solution #7

ca-scribner opened this issue Jul 25, 2024 · 2 comments

Comments

@ca-scribner
Copy link
Contributor

Enhancement Proposal

We need to design the upgrade procedure from another istio to this one. Some points to cover:

  • what if the Gateway CRDs already exist? Do we have conflicts during deployment?
  • how to we avoid deleting user data (eg: avoid deleting say the VirtualService CRD, which would delete all VirtualServices)
  • migrate charms using the old solution
@dstathis
Copy link
Contributor

We should have an official upgrade path from the Kubeflow version of istio. We should also have a few tips for upgrading from generic installations.

@dstathis
Copy link
Contributor

For the Kubeflow upgrade path, we should submit a PR to their repo which adds a config flag to not remove CRDs when the charm is removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dstathis @ca-scribner