VMware service stop stops the target system services running on a Linux OS based VMware VM.
- It determines the performance and resilience of the application (or service) running on the VMware VMs.
View the uses of the fault
- Kubernetes > 1.16
- Execution plane is connected to vCenter and the hosts on port 443.
- VMware tool is installed on the target VM with remote execution enabled.
- Adequate vCenter permissions to access the hosts and the VMs.
- Create a Kubernetes secret that has the Vcenter credentials in the
CHAOS_NAMESPACE. Below is a sample secret file:
You can pass the VM credentials as secrets or as a
ChaosEngine environment variable.
- The VM should be in a healthy state.
- The target services should exist inside the VM.
|VM_NAME||Name of the VM where the target processes reside.|| For example, |
|SERVICE_NAME||Name of the target service.|| For example, |
|SELF_HEALING_SERVICES|| Set to || Defaults to |
|TOTAL_CHAOS_DURATION||Duration that you specify, through which chaos is injected into the target resource (in seconds).||Defaults to 30s.|
|CHAOS_INTERVAL||Time interval between two successive instance terminations (in seconds).||Defaults to 30s.|
|SEQUENCE||Sequence of chaos execution for multiple instances.||Defaults to parallel. Supports serial sequence as well.|
|RAMP_TIME||Period to wait before and after injecting chaos (in seconds).||For example, 30s.|
Common fault tunables
Refer to the common attributes to tune the common tunables for all the faults.
It contains the target service name running on a particular VM.
Use the following example to tune this:
# Service Stop in the VMware VM
- name: VMware-service-stop
# Name of the VM
- name: VM_NAME
# Name of service
- name: SERVICE_NAME