Skip to content

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

Closed
@lucasvaltl

Description

@lucasvaltl

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    team: deliveryIssue belongs to the self-hosted team

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions