No, you can not use Chaos Mesh in this case. But still you can run chaos experiments using command line. Refer to Command Line Usages of Chaos for details.
You can try using the parameter:
hostNetwork, as shown below:
Q: I just saw
ERROR: failed to get cluster internal kubeconfig: command "docker exec --privileged kind-control-plane cat /etc/kubernetes/admin.conf" failed with error: exit status 1 when installing Chaos Mesh with kind. How to fix it?#
You can try the following command to fix it:
then deploy again.
You can debug as described below:
kubectl describe to check the specified chaos experiment resource.
If there are
spec, then the chaos will be triggered after
If there are no
spec, run the following command to get controller-manager's log and see whether there are errors in it.kubectl logs -n chaos-testing chaos-controller-manager-xxxxx (replace this with the name of the controller-manager) | grep "ERROR"
For error message
no pod is selected, run the following command to show the labels and check if the selector is desired.kubectl get pods -n yourNamespace --show-labels
Q: Running chaosfs sidecar container failed, and log shows
pid file found, ensure docker is not running or delete /tmp/fuse/pid#
The chaosfs sidecar container is continuously restarting, and you might see the following logs at the current sidecar container:
- Cause: Chaos Mesh uses Fuse to inject I/O failures. It fails if you specify an existing directory as the source path for chaos. This often happens when you try to reuse a persistent volume (PV) with the
Retainreclaim policy to request a PersistentVolumeClaims (PVC) resource.
- Solution: In this case, use the following command to change the reclaim policy to
Message most looked like this:
You need to add privileged scc to default.