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

Change the way how the crash loop buggify setting works #2080

Open
johscheuer opened this issue Jun 25, 2024 · 0 comments
Open

Change the way how the crash loop buggify setting works #2080

johscheuer opened this issue Jun 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@johscheuer
Copy link
Member

What would you like to be added/changed?

In the current implementation we change the arguments to crash-loop, this has the drawback that the Pod has to be recreated. In the recreation step (deletion and creation) the cluster state could be modified, so that the Pod is pending for some time. In addition, the recreation can take some time. A better and faster solution would be to change the image to a non existing image like localhost/foundationdb/crash-loop, this will keep the Pod running and will result in a similar setup.

@johscheuer johscheuer added the enhancement New feature or request label Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant