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

Gitlab Failover & High Availability Setup #410

Open
GitHK opened this issue Feb 5, 2021 · 0 comments
Open

Gitlab Failover & High Availability Setup #410

GitHK opened this issue Feb 5, 2021 · 0 comments
Assignees
Labels
Maintenance Maintenance for CI

Comments

@GitHK
Copy link
Contributor

GitHK commented Feb 5, 2021

In order to avoid blocking developer on all teams, we require a more stable GitLab installation which will bring better support in case of hardware/software issues.

To achieve this goal we like to have a deployment with the following:

  • tollerate 1 cluster node failure (service will still be available)
  • testable and reproducible environment for developers (to avoid surprises on the production cluster)
  • ability to self heal when the node is joined back to the cluster

  • automatic updates procedure
  • automatic data backup strategy in case total system failure (total data cancellation by accident)

Everything before the separator line is necessary

@drniiken drniiken added the Maintenance Maintenance for CI label Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Maintenance for CI
Projects
None yet
Development

No branches or pull requests

3 participants