Comments (4)
@mdnyeemakhtar I see. That is an interesting case. Let me get back on this.
from litmus-go.
chaosresult is a dedicated custom resource @rbalagopalakrishna . There is a case for it to exist independently (of chaosengine or its associated pods) in order to track failure/success history or generate some useful reports.
IMO a custom script/post-hook can be set up in case you are interested to remove them.
from litmus-go.
@ksatchit in our use case we are generating chaosengine name and it is unique for each execution so it generates new chaosresult each time. And so no history maintained in that case. We want the results to be delete along with engine. As of now we are doing it the way you suggested by custom script. However, we want a more robust and integrated solution for it in engine itself.
Can there be a flag in engine to delete results along with engine? By default it can be set to false and if someone (like us) needs it then they can enable it.
from litmus-go.
@mdnyeemakhtar I see. That is an interesting case. Let me get back on this.
Thank you @ksatchit
from litmus-go.
Related Issues (20)
- Add missing Jitter ENV input for Pod Network Chaos experiments HOT 2
- Add Status Logs to GCP experiments
- kubelet-service-kill experiment fails HOT 1
- pod-network-loss: cleanup fails because target pod has been restarted HOT 5
- pod cpu hog experiment fails due to litmus helper cgroup error. HOT 1
- Security vulnerabilities found on golang:1.17
- FEATURE - Add resource name filters inside the k8s probe
- Pod HTTP Status Code not working with Istio HOT 3
- Some questions for file experiment.go HOT 1
- PRISMA-2022-0164: Update github.com/aws/aws-sdk-go dependency to at least v1.40.27
- Capturing pod-fio-stress experiment metrics HOT 1
- DEFAULT_HEATTH_CHECK tunable does not disable all default verifications of AUTs pods. HOT 1
- Change the experiments "pod delete" and "pod Autoscaler" to support to Namespace dynamically HOT 2
- Node drain disruption not reverted after "kubectl drain" timeout
- Log all iterations of the probe for onchaos and continuous modes configured via verbosity flag HOT 1
- Litmus does not consider appKind when filtering the target pod for an experiment
- Add support for ALL for TARGET_CONTAINER for parallel executions
- CPU Hog Exec - is not terminating appropriately for certain target containers as intended HOT 1
- Fixes Vulnerabilities on promql and crictl binaries used inside the experiment image.
- pod-delete - TARGET_SELECTION_ERROR with custom parent Kind
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from litmus-go.