-
Notifications
You must be signed in to change notification settings - Fork 830
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
Added Controller for awsssmchaosrunner #1919
Conversation
* feat: workflow basic CRD and concilers Signed-off-by: STRRL <str_ruiling@outlook.com> * refactor(workflow): refine codes about determine conditions Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: the chaos node reconciler Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: add shor name for workflow and workflow node Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: events to describe creating chaos CR Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: add state for chaos cr created Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: tidy go.sum Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: preload go mod Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: partial updates Signed-off-by: STRRL <str_ruiling@outlook.com> * docs: update design docs Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: recover for chaos nodes Signed-off-by: STRRL <str_ruiling@outlook.com> * docs: update the docs Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: update the optioanl fields Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: update after make check Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: remove unused fields Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: fix the comments Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: fix typos Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: update the yaml Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: address the comments Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: reconstruct method orders Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: implmenetation of web api Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: make linters happy Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: address the comments Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: register workflow controller into fx Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: use empty slice instead of nil Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: cleanup unused states Signed-off-by: STRRL <str_ruiling@outlook.com> * refactor: determine running nodes out of the conversion funcs Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: remove the meaningless if Signed-off-by: STRRL <str_ruiling@outlook.com> * fix: update the entity used in swagger Signed-off-by: STRRL <str_ruiling@outlook.com> * fix: fix bugs with conversion workflow detail Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: determine node state Signed-off-by: STRRL <str_ruiling@outlook.com> * fix: do not apply networkchaos if condition injected is true Signed-off-by: STRRL <str_ruiling@outlook.com> * refactor: do not use the ambiguous name while in retry closures Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: update the workflow example Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: fmt the codes Signed-off-by: STRRL <str_ruiling@outlook.com> * refactor: conversation enitity and fix test cases Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: use clientpool instead of embedded kubeclient maybe we could use factory in the future Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: make linter happy Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: remove the current nodes in workflow detail Signed-off-by: STRRL <str_ruiling@outlook.com> * feat: hTTP API create and update of workflow Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: address the comments of muse-dev Signed-off-by: STRRL <str_ruiling@outlook.com> * fix: address the comments Signed-off-by: STRRL <str_ruiling@outlook.com> * chore: make linters happy Signed-off-by: STRRL <str_ruiling@outlook.com> Co-authored-by: Ti Chi Robot <71242396+ti-chi-bot@users.noreply.github.com> Signed-off-by: Debanitrkl <118BM0622@nitrkl.ac.in>
Signed-off-by: Debanitrkl <118BM0622@nitrkl.ac.in>
|
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
| }, | ||
| }, | ||
| } | ||
| e.Log.Info("Running the Container") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After creating the Pod, you should update the status of AwsChaos. It means you should also create new fields to describe the status of that created Pod.
And that status will be also used when Recover().
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah working on that
|
@Debanitrkl: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
I am going to close this PR because it seems not to be updated |
|
Can we put this in WIP I'm on a break and I will get back to this as soon as possible. |
What problem does this PR solve?
This is a controller for the integration of awsssmchaosrunner with chaos mesh according to this rfc.
What is changed and how does it work?
Added a file under
controllers/awschaoscalledattack-configurationTests
Related changes
Does this PR introduce a user-facing change?