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.

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

Provide a concept how user managed components can be migrated to kyma modules (once there is a module with same component) #18773

Open
2 tasks
abbi-gaurav opened this issue Jan 22, 2025 · 0 comments

Comments

@abbi-gaurav
Copy link
Member

abbi-gaurav commented Jan 22, 2025

Description

Example Scenario
I as a customer is using self-managed velero. After 1 year, Kyma sees value in velero and starts offering it as a module.
Now, how can I safely migrate to Kyma managed velero module with minimal or no disruptions.

This could be a part of module design and rollout. Without such guardrail, the migration to module from sef-managed component can be deemed as risky or complex.

Acceptance criteria

  • A step-by-step document which helps customer to migrate from their own managed component to Kyma module
  • Minimal to no disruption
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant