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.

Sign up for GitHub

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

Jump to bottom

Add E2E test for replica control and recoverability #35

Open
2 of 3 tasks
voltbit opened this issue Dec 1, 2020 · 0 comments
Open
2 of 3 tasks

Add E2E test for replica control and recoverability #35

voltbit opened this issue Dec 1, 2020 · 0 comments
Assignees
@voltbit
Labels
testing Code coverage and QA

Comments

@voltbit
Copy link
Contributor

voltbit commented Dec 1, 2020 •
edited
Loading

The process of recovering a node or updating the cluster can be long and with many steps. We have to introduce as many types of failures as possible to see that the controler is able to recover no matter which step of the process fails.
The test should at minimum be able to:

  • Restart containers or break Redis without taking the pod down
  • Delete pods
  • Disable Kubernetes nodes
@voltbit voltbit self-assigned this Dec 1, 2020
@voltbit voltbit added this to the Beta milestone Dec 1, 2020
This was referenced Dec 8, 2020
Merged
Closed
@voltbit voltbit added the testing Code coverage and QA label Jan 17, 2021
@voltbit voltbit removed this from the Beta milestone Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@voltbit voltbit

Labels
testing Code coverage and QA
Milestone
No milestone
Development

No branches or pull requests
1 participant
@voltbit