HCE and LitmusChaos
Harness Chaos Engineering (HCE) is powered by the open source CNCF chaos engineering project LitmusChaos. HCE adds additional features to make the practice of chaos engineering for enterprises easy.
Go to HCE versus LitmusChaos for a quick comparison.
Common capabilities of HCE and LitmusChaos
Following are the common features between Litmus and HCE:
- Scalable platform
- Declarative chaos fault architecture
- Kubernetes chaos faults
- Chaos faults as CRDs
- Chaos metrics
- Chaos hubs
- Chaos infrastructure architecture
- Chaos experiments structure
- Scheduling chaos experiments
- Resilience probes
Additional capabilities of HCE
HCE module has the following additional capabilities:
- Kubelet density chaos fault
- VMware chaos faults
- AWS chaos faults
- GCP chaos faults
- Azure chaos faults
- Linux chaos faults
- Windows chaos faults
- Cloud Foundry chaos faults
- Load chaos faults
- SSH chaos faults
- Kubernetes chaos faults
- Teaming around ChaosHubs
- Resilience probes (Dynatrace and Datadog)
- ChaosGuard
Integrations with other Harness modules
In addition to the above features, HCE integrates with these Harness modules:
- Continuous Delivery (CD): Go to Use HCE with CD.
- Feature Flags (FF): Go to Use HCE with FF.
- Service Reliability Management: Go to Use HCE SRM.
HCE free plans
Harness offers a free hosted LitmusChaos if you are trying to get started with LitmusChaos or Chaos Engineering in general. The HCE free plan is a free-forever plan that has features equivalent to LitmusChaos, and also bundles Harness platform features such as RBAC and hosted logging— all for free.
Sign up at app.harness.io to get started with a free plan for either the hosted HCE or the hosted LitmusChaos.
The HCE free plan replaces cloud.chaosnative.com. New sign ups are not being accepted at cloud.chaosnative.com. Users on that platform are advised to move to the HCE free plan before August 31, 2023. For free support on migration, contact Harness Support.
HCE versus LitmusChaos
This section describes the differences between Harness Chaos Engineering (HCE) and the open-source CNCF incubation project, LitmusChaos.
Chaos management - Basic
Feature | Litmus | HCE (SaaS) |
Centralized chaos portal | ✅ | ✅ |
Chaos hubs | Public hub | Enterprise hub |
Chaos metrics to Prometheus | ✅ | ✅ |
YAML-based support for chaos experiments | ✅ | ✅ |
Run chaos faults in parallel | ✅ | ✅ |
Experiment control parameters through the tag in the UI | ❌ | ✅ |
Event driven chaos injection | ✅ | ✅ (via Harness webhooks) |
Ability to halt all ongoing chaos experiments using the halt button | ❌ | ✅ |
BYOC (Bring Your Own Chaos) | ✅ | ✅ |
Chaos management - Advanced
Feature | Litmus | HCE (SaaS) |
Chaos experiments CRUD | Partial | ✅ |
Chaos experiments for multiple clusters | ❌ | ✅ (GameDays and pipelines) |
Run chaos experiments in parallel | ❌ | ✅ (GameDays and pipelines) |
Out-of-the-box chaos experiments | ❌ | ✅ |
OOTB API templates for chaos experiments | ❌ | ✅ |
Export chaos experiments to chaos hubs | ❌ | ✅ |
Schedule chaos scenarios directly from a chaos hub | ❌ | ✅ |
GameDay portal | ❌ | ✅ |
ChaosGuard | ❌ | ✅ |
Administration
Feature | Litmus | HCE (SaaS) |
Rest/GraphQL APIs | ✅ | ✅ |
Built-in user management and authentication | Basic | ✅ |
Single Sign-On (SSO) with OAuth 2.0 | ❌ | ✅ |
Single Sign-On (SSO) with SAML | ❌ | ✅ |
Provision users with Okta (SCM) | ❌ | ✅ |
Provision Azure AD Users and Groups (SCIM) | ❌ | ✅ |
Provision users and groups with OneLogin (SCIM) | ❌ | ✅ |
Multiple projects | ❌ | ✅ |
Multiple organisations | ❌ | ✅ |
Security
Feature | Litmus | HCE (SaaS) |
Two-factor authentication | ❌ | ✅ |
RBAC (Role Based Access Control)- Built-in roles | Basic | ✅ |
RBAC (Role Based Access Control)- Custom roles | ❌ | ✅ |
Audit trail (2 year data retention) | ❌ | ✅ |
Integrated secrets management with Harness Secrets Manager | ❌ | ✅ |
IP Address whitelist management | ❌ | ✅ |
Integrations
Feature | Litmus | HCE (SaaS) |
Integration with Harness Continuous Deployment Pipelines | ❌ | ✅ |
Integration with Jenkins Pipelines | ❌ | ✅ |
Integration with GitLab Pipelines | ❌ | ✅ |
Integration with Harness Continuous Verification | ❌ | ✅ |
Integration with Harness Feature Flags | ❌ | ✅ |
Integration with Service Reliability Management | ❌ | ✅ |
Kubernetes pod-level chaos faults
Go to Pod faults for more information.
Feature | Litmus | HCE (SaaS) |
Container kill | ✅ | ✅ |
Disk fill | ✅ | ✅ |
Pod API block kill | ❌ | ✅ |
Pod API latency | ❌ | ✅ |
Pod API modify body | ❌ | ✅ |
Pod API modify header | ❌ | ✅ |
Pod API status code | ❌ | ✅ |
Pod autoscaler | ✅ | ✅ |
Pod CPU hog exec | ✅ | ✅ |
Pod CPU hog | ✅ | ✅ |
Pod delete | ✅ | ✅ |
Pod DNS error | ✅ | ✅ |
Pod DNS spoof | ✅ | ✅ |
Pod HTTP reset peer | ✅ | ✅ |
Pod HTTP status code | ✅ | ✅ |
Pod HTTP modify body | ✅ | ✅ |
Pod HTTP modify header | ✅ | ✅ |
Pod HTTP latency | ✅ | ✅ |
Pod I/O attribute override | ❌ | ✅ |
Pod I/O error | ❌ | ✅ |
Pod I/O latency | ❌ | ✅ |
Pod I/O stress | ✅ | ✅ |
Pod memory hog exec | ✅ | ✅ |
Pod memory hog | ✅ | ✅ |
Pod network corruption | ✅ | ✅ |
Pod network duplication | ✅ | ✅ |
Pod network latency | ✅ | ✅ |
Pod network loss | ✅ | ✅ |
Pod network partition | ✅ | ✅ |
Pod network rate limit | ❌ | ✅ |
Time chaos | ❌ | ✅ |
Kubernetes node-level chaos faults
Go to Node faults for more information.
Feature | Litmus | HCE (SaaS) |
Kubelet service kill | ✅ | ✅ |
Node drain | ✅ | ✅ |
Node I/O stress | ✅ | ✅ |
Node CPU hog | ✅ | ✅ |
Node memory hog | ✅ | ✅ |
Node restart | ✅ | ✅ |
Node taint | ✅ | ✅ |
Node network latency | ❌ | ✅ |
Node network loss | ❌ | ✅ |
Kubernetes stress - Kubelet density | ❌ | ✅ |
AWS chaos faults
Go to Chaos faults for AWS for more information.
Feature | Litmus | HCE (SaaS) |
ALB AZ down | ❌ | ✅ |
CLB AZ down | ❌ | ✅ |
NLB AZ down | ❌ | ✅ |
EBS loss by ID | ✅ | ✅ |
EBS loss by tag | ✅ | ✅ |
EC2 DNS chaos | ❌ | ✅ |
EC2 instance stop by ID | ✅ | ✅ |
EC2 instance stop by tag | ✅ | ✅ |
AWS SSM chaos by ID | ✅ | ✅ |
AWS SSM chaos by tag | ✅ | ✅ |
EC2 network loss | ❌ | ✅ |
EC2 process kill | ❌ | ✅ |
EC2 stop by Id | ❌ | ✅ |
EC2 stop by tag | ❌ | ✅ |
EC2 network latency (Jitter/Abort) | ❌ | ✅ |
EC2 CPU hog | ❌ | ✅ |
EC2 memory hog | ❌ | ✅ |
EC2 I/O stress | ❌ | ✅ |
EC2 HTTP latency | ❌ | ✅ |
EC2 HTTP modify body | ❌ | ✅ |
EC2 HTTP modify header | ❌ | ✅ |
EC2 HTTP reset peer | ❌ | ✅ |
EC2 HTTP status code | ❌ | ✅ |
EC2 I/O stress | ❌ | ✅ |
RDS instance delete | ❌ | ✅ |
RDS instance reboot | ❌ | ✅ |
ECS instance kill | ❌ | ✅ |
ECS instance stop | ❌ | ✅ |
ECS task stop | ❌ | ✅ |
ECS task scale | ❌ | ✅ |
ECS invalid container image | ❌ | ✅ |
ECS network restrict | ❌ | ✅ |
ECS container network latency | ❌ | ✅ |
ECS container network loss | ❌ | ✅ |
ECS container volume detach | ❌ | ✅ |
ECS agent stop | ❌ | ✅ |
ECS container CPU hog | ❌ |