Files
litmus-hub/charts/gcp/gcp-vm-instance-stop/engine.yaml
Neelanjan Manna 755110178f GCP VM Instance Stop charts (#480)
* Added charts for GCP vm-instance-stop and vm-disk-loss experiments

* Removed temp file

* GCP charts updated for gcp-vm-instance-stop; removed vm-disk-loss experiment

* Added experiment image name

* Removed exec keyword, updated chaos interval

* Updated gcp charts messages

* Updated image tag to ci

* Updated experiment name in csv, removed exec

* Added charts for gcp-vm-disk-loss experiment

* Removed gcp-vm-disk-loss charts

* Removed experiment inputs and tagged the experiment image to ci

* Removed jobCleanupPolicy

* updated experiment description

* updated chartserviceversion description

* removed patch verb

Co-authored-by: Udit Gaurav <35391335+uditgaurav@users.noreply.github.com>
Co-authored-by: Shubham Chaudhary <shubham@chaosnative.com>
2021-07-15 12:35:07 +05:30

39 lines
1.3 KiB
YAML

apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
name: gcp-vm-chaos
spec:
engineState: 'active'
chaosServiceAccount: gcp-vm-instance-stop-sa
experiments:
- name: gcp-vm-instance-stop
spec:
components:
env:
# set chaos duration (in sec) as desired
- name: TOTAL_CHAOS_DURATION
value: '30'
# set chaos interval (in sec) as desired
- name: CHAOS_INTERVAL
value: '30'
# Instance name of the target vm instance(s)
# Multiple instance names can be provided as comma separated values ex: instance1,instance2
- name: VM_INSTANCE_NAMES
value: ''
# GCP project ID to which the vm instances belong
- name: GCP_PROJECT_ID
value: ''
# Instance zone(s) of the target vm instance(s)
# If more than one instance is targetted, provide zone for each in the order of their
# respective instance name in VM_INSTANCE_NAME as comma separated values ex: zone1,zone2
- name: INSTANCE_ZONES
value: ''
# enable it if the target instance is a part of self-managed auto scaling group.
- name: AUTO_SCALING_GROUP
value: 'disable'