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

Feature Request: Add info about the resources under chaos #335

Closed
HristoDaskalovDev opened this issue Feb 15, 2021 · 2 comments
Closed

Feature Request: Add info about the resources under chaos #335

HristoDaskalovDev opened this issue Feb 15, 2021 · 2 comments

Comments

@HristoDaskalovDev
Copy link

Feature Request: Add info about the resources under chaos

Feature request
What happened: ChaosEngine and ChaosResult do not contain information about the specific target of the chaos.
For instance if I leave the 'appLabel' field empty, when the engine executes, how will I know on which pod, exactly did the chaos happen. Even if appLabel is filled, it would still be
helpful to know the targets of the chaos. I can only see the targeted pod if i look at the logs of the helper pod.
What you expected to happen: I expect to be able to see the names of the pods, that the ChaosEngine is injecting chaos into, as well as the deployment they belong to. Either in the
ChaosEngine or the ChaosResult.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: A 'nice to have' would be to have a verdict (from ChaosResult) for each unique deployment. For example if 1 ChaosEngine does pod-kill on 3 pods, each from
a different deployment and the verdict is Fail, does this mean that one of them failed or all 3 ?

@ksatchit
Copy link
Member

ksatchit commented Feb 15, 2021

This is a great requirement & a very useful one!!

@neelanjan00
Copy link
Member

We added this here: litmuschaos/litmus-go#336, thanks for raising this issue! :)

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

3 participants