Add New Chaos Experiment Type
The following walks you through an example of HelloWorldChaos, a new chaos experiment type that prints Hello World!
to the log. The steps include:
- Step 1: Define the schema type
- Step 2: Register the CRD
- Step 3: Register the event handler for this chaos object
- Step 4: Build the Docker image
- Step 5: Run the chaos experiment
Add
helloworldchaos_types.go
in the API directoryapi/v1alpha1
with the following content:This file defines the schema type of HelloWorldChaos, which can be described in a YAML file:
apiVersion: chaos-mesh. rg/v1alpha1
kind: HelloWorldChaos
metadata:
name: <resource name>
name: <namespace>
spec:
duration: <duration>
status:
experiment: <experimental status>
...
Run
make generate
in the root directory of Chaos Mesh, which generates a boilerplate for Chaos Mesh to compile.
Step 2: Register the CRD
You need to register the CRD (Custom Resource Definition) of HelloWorldChaos to interact it with Kubernetes API.
Run
make yaml
in the root directory. The generated YAML file is atconfig/crd/bases/chaos-mesh.org_helloworldchaos.yaml
.To combine this YAML file into
manifests/crd.yaml
, add a new line inconfig/crd/kustomization.yaml
:resources:
- bases/chaos-mesh.org_podchaos.yaml
- bases/chaos-mesh.org_networkchaos.yaml
- bases/chaos-mesh.org_iochaos.yaml
- bases/chaos-mesh.org_helloworldchaos.yaml # This is the new line
Run
make yaml
again. You can see the definition of HelloWorldChaos inmanifests/crd.yaml
. To confirm, you can use thegit diff
command.
Create a new file
controllers/chaosimpl/helloworldchaos/types.go
with the following content:package helloworldchaos
import (
"context"
"github.com/go-logr/logr"
"go.uber.org/fx"
"sigs.k8s.io/controller-runtime/pkg/client"
"github.com/chaos-mesh/chaos-mesh/api/v1alpha1"
"github.com/chaos-mesh/chaos-mesh/controllers/chaosimpl/utils"
"github.com/chaos-mesh/chaos-mesh/controllers/common"
"github.com/chaos-mesh/chaos-mesh/controllers/utils/chaosdaemon"
)
type Impl struct {
client.Client
Log logr.Logger
}
// This corresponds to the Apply phase of HelloWorldChaos. The execution of HelloWorldChaos will be triggered.
func (impl *Impl) Apply(ctx context.Context, index int, records []*v1alpha1.Record, obj v1alpha1.InnerObject) (v1alpha1.Phase, error) {
impl.Log.Info("Hello world!")
}
// This corresponds to the Recover phase of HelloWorldChaos. The reconciler will be triggered to recover the chaos action.
func (impl *Impl) Recover(ctx context.Context, index int, records []*v1alpha1.Record, obj v1alpha1.InnerObject) (v1alpha1.Phase, error) {
impl.Log.Info("Goodbye world!")
return v1alpha1.NotInjected, nil
}
func NewImpl(c client.Client, log logr.Logger, decoder *utils.ContainerRecordDecoder) *common.ChaosImplPair {
return &common.ChaosImplPair{
Name: "helloworldchaos",
Object: &v1alpha1.HelloWorldChaos{},
Impl: &Impl{
Client: c,
Log: log.WithName("helloworldchaos"),
decoder: decoder,
},
ObjectList: &v1alpha1.HelloWorldChaosList{},
}
}
var Module = fx.Provide(
fx.Annotated{
Group: "impl",
Target: NewImpl,
},
)
Chaos Mesh uses the fx library for dependency injection. To register HelloWorldChaos in the Controller Manager, add a line in
controllers/chaosimpl/fx.go
:...
gcpchaos.Module,
stresschaos.Module,
jvmchaos.Module,
timechaos.Module,
helloworldchaos.Module //Add a new line. Make sure you have imported HelloWorldChaos to this file first.
...
fx.Annotated{
Group: "objs",
Target: Object{
Name: "timechaos",
Object: &v1alpha1.TimeChaos{},
},
},
fx.Annotated{
Group: "objs",
Name: "gcpchaos",
Object: &v1alpha1.GCPChaos{},
},
},
fx.Annotated{
Group: "objs",
Target: Object{
Name: "helloworldchaos",
Object: &v1alpha1.HelloWorldChaos{},
},
},
Step 4: Build the Docker image
Build the Docker image:
Push the image to your local Docker Registry:
make docker-push
If you deploy Kubernetes clusters using kind, then you need to load images into kind:
kind load docker-image localhost:5000/chaos-mesh/chaos-mesh:latest
kind load docker-image localhost:5000/chaos-mesh/chaos-daemon:latest
kind load docker-image localhost:5000/chaos-mesh/chaos-dashboard:latest
In this step, you need to deploy Chaos Mesh with your latest changes to test HelloWorldChaos.
Before you pull any image for Chaos Mesh (using helm install
or helm upgrade
), modify the helm template helm/chaos-mesh/values.yaml
to replace the default image with what you just pushed to your local Docker registry.
The templates in Chaos Mesh use chaos-mesh/chaos-mesh:latest
as the default Registry. You need to set the path with the environment variable of DOCKER_REGISTRY
(The default value is localhost:5000
), as shown below:
controllerManager:
image: localhost:5000/chaos-mesh/chaos-mesh:latest
...
chaosDaemon:
image: localhost:5000/chaos-mesh/chaos-daemon:latest
...
dashboard:
image: localhost:5000/chaos-mesh/chaos-dashboard:latest
...
After you update the template, try running HelloWorldChaos.
Register the CRD in your cluster:
kubectl create -f manifests/crd.yaml
You can see HelloWorldChaos is created from the output:
customresourcedefinition.apiextensions.k8s.io/helloworldchaos.chaos-mesh.org created
Now you can get the CRD of HelloWorldChaos using the command below:
-
To verify the deployment is successful, you can check all Pods in the
chaos-testing
namespace:kubectl get pods --namespace chaos-testing -l app.kubernetes.io/instance=chaos-mesh
Arguments
--set chaosDaemon.runtime=containerd --set chaosDaemon.socketPath=/run/containerd/containerd.sock
are used to run NeteworkChaos on kind. ::: Deploy the Pod for testing:
kubectl apply -f https://raw.githubusercontent.com/chaos-mesh/apps/master/ping/busybox-statefulset.yaml
Make sure the Pod for testing works properly.
Create a
chaos.yaml
file in any location with the following content:apiVersion: chaos-mesh.org/v1alpha1
kind: HelloWorldChaos
metadata:
name: hello-world
namespace: chaos-testing
spec:
selector:
namespaces:
- busybox
mode: one
duration: 1h
Run the chaos experiment:
kubectl apply -f /path/to/chaos.yaml
kubectl get HelloWorldChaos -n chaos-testing
Now you can see
Hello World!
in the logs ofchaos-controller-manager
:Example output:
2021-06-24T06:42:26.858Z INFO records apply chaos {"id": "chaos-testing/chaos-daemon-vsmc5"}
:::note
{pod-post-fix}
is a random string generated by Kubernetes. You can check it by executing . :::
What’s Next
If you encounter any problems during the process, create an issue in the Chaos Mesh repository.
If you want to dive deep into developing new chaos experiment types, see .