Skip to main content

ChaosHub

ChaosHub​

A ChaosHub is a collection of experiment templates (defined as workflow custom resources) and faults (defined as ChaosExperiment CR and ChaosEngine CR) that you can use to create and launch chaos experiments. Both experiments and faults are stored as manifests in an appropriate directory structure. This way, you can add new experiment templates and faults directly to the repository as files. In addition, you can derive the experiment templates from the existing experiments and save them to the ChaosHub from the UI.

You can add ChaosHub using a Git service provider such as GitHub, where ChaosHub exists as a repository. This allows native version control and management of the faults and experiment artefact.

HCE provides a default Enterprise ChaosHub that includes a wide array of experiments and faults out of the box. You can also add your own custom ChaosHubs to maintain and share private scenarios and faults within your organization.

Permissions required​

ChaosHubs are associated with chaos experiments, hence you need permissions to create new experiments and modify exisiting experiments. Chaos experiments, in turn, are executed in a chaos infrastructure, hence you need to have access to create/edit and view the chaos infrastructure. Go to Project Settings -> Access Control -> Roles and create a new role or ask your project admin to create an appropriate role.

Enterprise ChaosHub​

It is a ChaosHub with additional security and teaming features for better collaboration around chaos scenarios. It is a private GitHub repository that you can access using a special key.

Also known as Enterprise hub, it comes out-of-the-box with HCE and consists of pre-built manifests (YAML files) and chaos experiment templates. It is a prebuilt ChaosHub that represents the existing experiments and chaos faults. You can use faults from multiple categories to create chaos experiments in the Enterprise ChaosHub.

Use cases of ChaosHubs​

  • You can get secure storage of your git keys. except admins, no one else can access your git keys.
  • You can export a given chaos scenario to an Enterprise ChaosHub. Once you export a chaos scenario, it is hosted in the hub and is ready to be used as a base for cloning.
  • You get access to many chaos scenarios in the Enterprise hub where you can browse through a scenarios and directly execute it.

Reason for adding custom ChaosHub​

  • Add custom experiments suited to specific needs in your organization.
  • Share your experiments with others in your Harness project or in other Harness projects—you can add the same custom hub(s) to many projects.
  • Maintain and upgrade experiments in one place so those you share your hubs with always have the latest version.
  • Provide secure access to your custom experiments.
note

Resilience probes are currently not supported with Chaos Hubs.

Go to connect to ChaosHub or manage ChaosHub for hands-on learning.