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

Failure Scenario: Loss of Kubernetes Cluster #130

Open
eriksw opened this issue Feb 21, 2019 · 0 comments
Open

Failure Scenario: Loss of Kubernetes Cluster #130

eriksw opened this issue Feb 21, 2019 · 0 comments

Comments

@eriksw
Copy link

eriksw commented Feb 21, 2019

This might just be an issue of documentation, but what are the steps to restore a backup when the backup CRD isn't there but the data does still exist in S3?

There are two variants of this scenario, but I suspect the steps are the same:

  1. The Kubernetes cluster where the backup was created is still running, but I want to restore the data into a different Kubernetes cluster. (In a different cloud/region/IAAS account, etc...)
  2. The Kubernetes cluster where the backup was created is a total loss and I'm restoring into a replacement. (Kubernetes' etcd wiped with no backup, IAAS volumes destroyed, etc...)
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