Skip to content

[Self-Hosted] Way to persist Gitpod Installation Config for Disaster Recovery Purposes #10549

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

Closed
lucasvaltl opened this issue Jun 9, 2022 · 1 comment
Labels
team: delivery Issue belongs to the self-hosted team

Comments

@lucasvaltl
Copy link
Contributor

lucasvaltl commented Jun 9, 2022

Is your feature request related to a problem? Please describe

Currently, when thinking about self-hosted Gitpod from a disaster Recovery perspective, we recommend that you use external dependencies (e.g. cloud provider SQL database) and the respective best practice backup strategy for it. However, this would mean you currently would need to re-input your installation configuration when trying to restore Gitpod. This impacts time to recovery.

Describe the behaviour you'd like

A way to persist the installation config of Gitpod and be able to re-use it to restore Gitpod to the previously well known state.

Potential solution

One way would be to explicitly document the configuration and the kots CLI (non ui) installation path and then expect users to use this.

Additional context

@lucasvaltl lucasvaltl added the team: delivery Issue belongs to the self-hosted team label Jun 9, 2022
@lucasvaltl lucasvaltl changed the title {Self-Hosted] Way to persist Gitpod Installation Config for Disaster Recovery Purposes [Self-Hosted] Way to persist Gitpod Installation Config for Disaster Recovery Purposes Jun 9, 2022
@lucasvaltl
Copy link
Contributor Author

Replaced by #10719

Repository owner moved this from 🧊Backlog to ✨Done in 🚚 Security, Infrastructure, and Delivery Team (SID) Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team: delivery Issue belongs to the self-hosted team
Projects
No open projects
Development

No branches or pull requests

1 participant