chaos-experiment
Create and manage chaos experiments using Harness Chaos Engineering via MCP. Run resilience tests like pod deletion, CPU stress, and network faults. Use when user says "chaos experiment", "chaos engineering", "resilience test", "chaos test", or wants to test system reliability.
- License 许可
- Apache-2.0
- 最近更新
- 2026-06-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- chaos-experiment
- license
- Apache-2.0
- metadata
- { "author": "Harness", "version": "2.0.0", "mcp-server": "harness-mcp-v2" }
- description
- Create and manage chaos experiments using Harness Chaos Engineering via MCP. Run resilience tests like pod deletion, CPU stress, and network faults. Use when user says "chaos experiment", "chaos engineering", "resilience test", "chaos test", or wants to test system reliability.
- compatibility
- Requires Harness MCP v2 server (harness-mcp-v2)
03 SKILL.md 正文
Chaos Experiment
Create and manage chaos experiments using Harness Chaos Engineering via MCP.
Instructions
Step 1: Check Infrastructure
Call MCP tool: harness_list
Parameters:
resource_type: "chaos_infrastructure"
org_id: "<organization>"
project_id: "<project>"
Step 2: Browse Templates
Call MCP tool: harness_list
Parameters:
resource_type: "chaos_experiment_template"
org_id: "<organization>"
project_id: "<project>"
Step 3: List Existing Experiments
Call MCP tool: harness_list
Parameters:
resource_type: "chaos_experiment"
org_id: "<organization>"
project_id: "<project>"
Step 4: Create Experiment
Call MCP tool: harness_create
Parameters:
resource_type: "chaos_experiment"
org_id: "<organization>"
project_id: "<project>"
body: <experiment definition>
Step 5: Run Experiment
Call MCP tool: harness_execute
Parameters:
resource_type: "chaos_experiment"
action: "run"
resource_id: "<experiment_id>"
org_id: "<organization>"
project_id: "<project>"
Step 6: Monitor Results
Call MCP tool: harness_list
Parameters:
resource_type: "chaos_experiment_run"
org_id: "<organization>"
project_id: "<project>"
Get specific run details:
Call MCP tool: harness_get
Parameters:
resource_type: "chaos_experiment_run"
resource_id: "<run_id>"
Step 7: Check Probes
Call MCP tool: harness_list
Parameters:
resource_type: "chaos_probe"
org_id: "<organization>"
project_id: "<project>"
Common Experiment Types
- Pod Delete - Kill pods to test recovery
- Pod CPU Hog - Stress CPU to test throttling
- Pod Memory Hog - Consume memory to test OOM handling
- Pod Network Loss - Simulate network failures
- Pod Network Latency - Add artificial latency
- Node Drain - Drain K8s nodes
- EC2 Stop - Stop AWS EC2 instances
- ECS Task Stop - Stop ECS tasks
Chaos Resource Types
| Resource Type | Operations | Description |
|---|---|---|
chaos_experiment |
list, get, create, update, delete, run | Experiments |
chaos_experiment_run |
list, get | Run history/results |
chaos_experiment_template |
list, get | Pre-built templates |
chaos_infrastructure |
list, get | Target infrastructure |
chaos_probe |
list, get | Health probes |
Examples
- "Show me all chaos experiments" - List chaos_experiment
- "Create a pod-delete experiment for checkout-service" - Create chaos_experiment
- "Run the weekly resilience test" - Execute run action
- "What were the results of the last chaos run?" - Get chaos_experiment_run
Performance Notes
- Review existing experiments before creating duplicates. Check for similar fault types targeting the same service.
- Wait for experiment completion before analyzing results. Do not draw conclusions from partial runs.
- Verify the target infrastructure and service are healthy before running chaos experiments.
Troubleshooting
Experiment Won't Run
- Verify chaos infrastructure is connected and active
- Check target application/namespace exists
- Ensure RBAC permissions for chaos operations
Probes Failing
- Check probe endpoints are accessible
- Verify probe timeout settings
- Review probe type matches expected behavior
04 同仓库更多 Skills
verify-sign
Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.
template-usage
Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).
sign-artifact
Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build/push; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.
sei-analytics
Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.
security-report
Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says "security report", "vulnerabilities", "SBOM", "security scan", "compliance check", or asks about application security.
scorecard-review
Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says "scorecard", "service maturity", "production readiness", "compliance score", or asks about service health scores.