FAQs

    No. Instead, you could use chaosd to inject failures without kubernetes.

    Q: I have deployed Chaos Mesh and created PodChaos experiments successfully, but I still failed in creating NetworkChaos/TimeChaos Experiment. The log is shown as below:

    The reason is that chaos-controller-manager failed to connect to chaos-daemon. You need to first check the Pod network and its policies.

    If everything is in order, maybe you can use the hostNetwork parameter to fix this problem as follows:

    Reference: 

    1. kind: ClusterRole
    2. apiVersion: rbac.authorization.k8s.io/v1
    3. metadata:
    4. rules:
    5.   - apiGroups: ['']
    6.     resources: ['pods', 'namespaces']
    7.     verbs: ['get', 'watch', 'list']
    8.   - apiGroups:
    9.       - chaos-mesh.org
    11.     verbs: ['get', 'list', 'watch', 'create', 'delete', 'patch', 'update']
    12. ---
    13. kind: ClusterRoleBinding
    14. apiVersion: rbac.authorization.k8s.io/v1
    15. metadata:
    16.   name: cluster-manager-binding
    17. subjects:
    18.   # Google Cloud user account
    19.   - kind: User
    20.     name: USER_ACCOUNT
    21. roleRef:
    22.   kind: ClusterRole
    23.   name: role-cluster-manager-pdmas

    The USER_ACCOUNT above should be your Google Cloud user email.

    Q: Daemon throws an error similar to version 1.41 is too new. The maximum supported API version is 1.39

    This indicates that the maximum API version that the Docker daemon can accept is 1.39, but the client in chaos-daemon uses 1.41 by default. You can choose the following options to solve this problem:

    1. Upgrade your Docker to a newer version.
    2. Helm install/upgrade with --set chaosDaemon.env.DOCKER_API_VERSION=1.39.

    If the error message is similar to the following:

    You need to add the privileged Security Context Constraints (SCC) to the chaos-dns-server.

    1. oc adm policy add-scc-to-user privileged -n chaos-testing -z chaos-dns-server

    Q: While trying to install Chaos Mesh in OpenShift, the problems regarding authorization blocked the installation process

    You need to add privileged scc to default.

    1. oc adm policy add-scc-to-user privileged -n chaos-testing -z chaos-daemon

    This issue occurs when you install Chaos Mesh on Kubernetes v1.15 or an earlier version. We use apiextensions.k8s.io/v1 by default, but it was introduced in Kubernetes v1.16 on 2019-09-19.

    When you install Chaos Mesh on Kubernetes lower than v1.16, you need to follow the below process:

    1. Manually create CRD through https://mirrors.chaos-mesh.org/<chaos-mesh-version>/crd-v1beta1.yaml.
    2. Use Helm to finish the rest process of installation, and append --skip-crds with command.

    We suggest upgrading your Kubernetes cluster by referencing Kubernetes Version Skew Policy.