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

feat: importing existing clusters #546

Open
george-pogosyan opened this issue Jul 24, 2024 · 3 comments
Open

feat: importing existing clusters #546

george-pogosyan opened this issue Jul 24, 2024 · 3 comments

Comments

@george-pogosyan
Copy link

george-pogosyan commented Jul 24, 2024

It would be great, if everest could import existing cluster, created with percona's operators when installing in namespace.

@spron-in
Copy link

spron-in commented Aug 5, 2024

@george-pogosyan it is something on our radar. I would appreciate if you can share more about your use case either here or we can jump into a call to discuss it. (feel free to book me here: https://scheduler.zoom.us/percona-sergey-pronin/30-mins)

@kylemclaren
Copy link

What's blocking this, roughly? Trying to figure out if it would feasible trying to build a shim so we can manage pg-operator instances from Everest.

@PeterSzcz
Copy link

Hi @kylemclaren

I don't think anything specific is blocking this feature, we need to make sure the CRDs are compatible when "connecting" existing cluster to Everest and provide UI/API/CLI methods to perform this operation. I think the biggest effort will be to QA this feature for all 3 DB technologies we currently support. One of our priorities for Q1 2025 is ability to "import" databases to Everest from various sources like backups or "downtimeless" using DB replication. We need to discuss internally as another option "connecting" databases managed with operators to Everest.

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

4 participants