Releases: litmuschaos/litmus
Releases · litmuschaos/litmus
1.4.0-RC2
[Cherry-pick for RC2] (#1506) * update(pod-delete): Adding type casting in pod-delete experiment (#1503) Signed-off-by: shubhamchaudhary <[email protected]> * feat(disk-fill): Adding Dynamic Variable for Container Path (#1502) * (feat) Adding Dynamic Variable for Container Path Signed-off-by: Rahul M Chheda <[email protected]> * Adding appropriate comments Signed-off-by: Rahul M Chheda <[email protected]> * feat(image): Using a comman image for stress-ng commands (#1462) Signed-off-by: Udit Gaurav <[email protected]> Co-authored-by: Rahul M Chheda <[email protected]> Co-authored-by: UDIT GAURAV <[email protected]>
1.4.0-RC1
update(disk-loss):Adding lib env in disk-loss experiment (#1457) Signed-off-by: shubhamchaudhary <[email protected]>
1.3.0
New Features and Enhancements
- Introduces admin mode of chaos execution by which all chaos resources can be maintained in a single namespace while injecting chaos on applications across multiple namespaces
- Introduces helm charts for litmus infrastructure components and chaos charts
- Supports download of versioned chaos chart bundles on the chaoshub
- Supports custom/user-specified annotation filters to determine application chaos candidates
- Makes the chaos exporter a cluster-wide component deployed alongside the operator to extract metrics for all chaosengines
- Adds increased Kubernetes events to track failures (ex: inability to create chaos resources, access/patch chaosengine etc.,)
- Adds ability to re-trigger experiments for completed chaosengines via a patch operation
- Adds OpenEBS NFS provisioner failure experiment with external liveness checks to verify provisioner functionality & data persistence
- Introduces the Cassandra chaos chart with cassandra node failure experiment along with external liveness checks to perform database CRUD operations during chaos
- Adds pod level memory hog experiment with provision for users to provide memory to consume (in MB)
- Enhances the chaostoolkit based pod delete experiment to use python modules with added support for a json (blob) result artifact and different failure modes (i.e., single/multi pod failure)
- Enhances the node cpu hog experiment to accept cpu core count as a user input
- Enhances the container kill experiment to repeat chaos actions over a total chaos duration instead of being a single-action test
- Restructures the chaoslib to categorize chaos injection functions/taskfiles under respective tool-based lib
- Improves the experiment logs (task banners) based on the category/function performed by the tasks
- Adds (aquasecurity) trivy based static security scans for all litmus component images as part of respective CI builds
- Includes lint-checks with custom/project-specific rules for ansible playbooks in litmus CI build
- Improves the litmus e2e pipelines with addition of new tests around admin mode, multiple parallel chaosengine execution across namespaces, validation for engine status patch
- Improves e2e infra (scripts) to be able to launch e2e pipelines with custom image versions
- Adds pipeline history information in the litmus-e2e repo to track experiment status
- Introduces a new repo to hold charts and experiment icons linked to respective CSVs on the chaoshub.
- Adds documentation to explain the plugin model in litmus and integration with other chaos tools
- Adds a new artifact in the litmus repository called releases to track salient resource schema changes and provide references to detailed release notes
Major Bug Fixes
- Fixes the incorrect experiment status on chaosengine (“Awaited”) despite completion of experiment
- Fixes failure to schedule auxiliary/helper pods with nodeSelector specification on EKS clusters
- Fixes ambiguity/missing steps in developer guide and updates experiment artefacts templates with latest changes (since v1.0)
- Fixes the event source names in case of events generated by chaos-runners to bear chaos-runner pod name
- Fixes the failure to verify successful app reschedule post drain operation in node-drain experiment
- Fixes the crash of powerfulseal deployment due to use of improper service account
Getting Started
Prerequisites to install
- Make sure you have a healthy Kubernetes Cluster.
- Kubernetes 1.11+ is installed
Installation
kubectl apply -f https://litmuschaos.github.io/litmus/litmus-operator-v1.3.0.yaml
Verify your installation
-
Verify if the chaos operator is running
kubectl get pods -n litmus -
Verify if chaos CRDs are installed
kubectl get crds | grep chaos
For more details refer to the documentation at Docs
1.3.0-RC1
1.2.2
(Review): Adding OpenEBS NFS provisioner kill experiment (#1248) (#1397) * (feat): Adding OpenEBS NFS provisioner kill experiment Signed-off-by: Raj <[email protected]>
1.2.1
1.2.0
New features and Enhancements
- Addition of Chaos Events (across all litmus components, i.e., operator/runner/experiment job) to indicate experiment lifecycle
- Enhanced ChaosResult with experiment failure reason (step) provided in CR status
- Includes Node Memory Hog experiment to generic/kubernetes suite
- Includes OpenEBS pool disk loss experiment for GKE/AWS
- Adds support for Amazon EKS platform for generic chaos experiments
- Introduces a new chart category based on chaostoolkit with initial pod chaos experiments
- Supports override of default runner properties such as imagePullPolicy & entrypoint/args
- Extends cleanupPolicy enforcement to chaos-runner pods (apart from just the experiment job) with improved reconciliation flow
- Improves experiment chaoslib which now makes use of jobs (replacing daemonsets) to reduce the number of chaos resources (pods) used in an experiment, with chaos injection commands burned into the job templates.
- Adds support for RAMP_UP / RAMP_DOWN periods during the course of a chaos experiment.
- Homogenizes the time units (sec over msec) used across experiments for chaos duration and other parameters.
- Improved e2e suite with Ginkgo based BDD tests for newly added experiments and operator functionality
- Refactors the test-tools repository structure based on tool type
- Introduces an NFS liveness tool to lay foundation for NFS storage chaos experiments
- Adds governance artefacts (Maintainers, Governance) along with the project roadmap and an initial set of public adopters of LitmusChaos
- Adds license dependencies and scan reports obtained via fossa
Major Bug Fixes
- Fixes the hardcoded total chaos/job wait duration in the node-cpu-hog experiment.
- Fixes to verify state of application pods (health check) before proceeding with subsequent iterations of pod-delete chaos
- Adds a unique instance_id/run_id (hash) to names & labels of chaos jobs started by the experiment to aid identification and prevent conflicts upon parallel or repeated runs in a given namespace.
- Fixes execution workflow of chaos experiments when run as a standalone job without orchestration by the chaos operator
Getting Started
Prerequisites to install
- Make sure you have a healthy Kubernetes Cluster.
- Kubernetes 1.11+ is installed
Installation
kubectl apply -f https://litmuschaos.github.io/litmus/litmus-operator-v1.2.0.yaml
Verify your installation
-
Verify if the chaos operator is running
kubectl get pods -n litmus -
Verify if chaos CRDs are installed
kubectl get crds | grep chaos
For more details refer to the documentation at Docs
1.2.0-RC1
(chore)roadmap: add issue links to near term roadmap items (#1285) * (chore)roadmap: add issue links to near term roadmap items Signed-off-by: ksatchit <[email protected]> Co-authored-by: Shubham Chaudhary <[email protected]>
1.1.1
1.1.0
New features and Enhancements
- Addition of OpenEBS control-plane sanity, storage pool sanity & storage pool network chaos experiments
- Introduce the Chaos Abort functionality to terminate in-flight chaos experiments at once
- Schema changes to support override of configmap & secret volumes parameters from the ChaosEngine with improved component structure
- Make annotation checks against target applications an optional feature in lieu of infra chaos experiments with higher blast radius (multi-application impact).
- Make the Go Chaos-Runner as the default runner type for experiments
- Improved CRD validation for ChaosEngine CRs based on OpenAPI v3 specification
- Improved logging for experiment lifecycle (chaos-runner) via use of klog framework
- Addition of Kubernetes events for chaos experiment lifecycle
- Enhancement to pass chaos lineage (chaos UUID) across all resources created as part of an experiment
- Strengthened e2e pipelines (generic, openebs chaos validation tests) with BDD tests using Ginkgo
- Updates experiment scaffold (developer) tool to reflect latest experiment schema
- Optimized (minimal) permissions in the chaos-operator RBAC
- Converts the chaos-charts repo into the single source truth wrt chaos manifests (includes experiment RBAC, sample ChaosEngine CR manifests along with individual chaosExperiment CRs & CSV) thereby providing an integrated bundle to aid developers
- Doc updates to embed all chaos snippets from chaos-charts via the embedmd tool
- Adds the Litmus FAQ with questions on general usage & troubleshooting steps
Major Bug Fixes
- Addition of rescue blocks in chaoslib wrappers to fail fast / avoid false positives in chaos experiments
- Fixes container-kill experiment execution on containerd runtime
- Patch chaosresult state with status “running” & verdict “awaited” during experiment execution.
- Fixes crash of exporter (monitor pod) in case of infra experiments with annotationCheck disabled.
- Refactor of experiment manifests to use standard naming conventions & file extensions
Getting Started
Prerequisites to install
- Make sure you have a healthy Kubernetes Cluster.
- Kubernetes 1.11+ is installed
Installation
kubectl apply -f https://litmuschaos.github.io/litmus/litmus-operator-v1.1.0.yaml
Verify your installation
-
Verify if the chaos operator is running
kubectl get pods -n litmus -
Verify if chaos CRDs are installed
kubectl get crds | grep chaos
For more details refer to the documentation at Docs