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

Optimize chaosblade resource state flow in k8s experiments #336

Closed
xcaspar opened this issue Apr 22, 2020 · 0 comments
Closed

Optimize chaosblade resource state flow in k8s experiments #336

xcaspar opened this issue Apr 22, 2020 · 0 comments
Labels
chaosblade-operator chaosblade-operator project type/enhancement New feature or request
Milestone

Comments

@xcaspar
Copy link
Member

xcaspar commented Apr 22, 2020

Issue Description

Type: enhance request

Describe what happened (or what feature you want)

  1. When destroying the experiment fails, it will cause the problem of destroying all the time.
  2. When chaosblade-operator is restarted, chaosblade resources may be recreated.

Describe what you expected to happen

  1. Even if the execution fails, it will not return requeue or error.
  2. Re-creation is allowed only when the state is Initial, and Initialized state is added to avoid the condition that the experiment has been created but the state update fails.
  3. Add the --force-remove flag to solve the problem that the experiment cannot be deleted.
  4. When updating the blade resource spec, the previous spec will be added to metadata.annotations to destroy previous experiments.

Tell us your environment

Anything else we need to know?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chaosblade-operator chaosblade-operator project type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant