updated azure AZURE_INSTANCE_NAMES and gcp ZONES envs (#571)

Signed-off-by: Neelanjan Manna <neelanjan.manna@harness.io>

Signed-off-by: Neelanjan Manna <neelanjan.manna@harness.io>

charts/gcp/experiments.yaml

@@ -76,7 +76,7 @@ spec:
     # set the disk zone(s) as comma seperated values in the corresponding 
     # order of DISK_VOLUME_NAME  
     # eg. zone1,zone2,...
-    - name: DISK_ZONES
+    - name: ZONES
       value: ''
       
     labels:
@@ -152,7 +152,7 @@ spec:
 
     # set the zone in which all the disks are created
     # all the disks must exist in the same zone 
-    - name: DISK_ZONES
+    - name: ZONES
       value: ''
     
     # set the label of the target disk volumes
@@ -248,7 +248,7 @@ spec:
     
     # Zone in which the target vm instance(s) filtered by the label exist
     # all the instances should lie in a single zone
-    - name: INSTANCE_ZONES
+    - name: ZONES
       value: ''
     
     # enable it if the target instance is a part of a managed instance group
@@ -359,7 +359,7 @@ spec:
     # 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
+    - name: ZONES
       value: ''
       
     labels:

charts/gcp/gcp-vm-disk-loss-by-label/engine.yaml

@@ -24,7 +24,7 @@ spec:
 
             # set the zone in which all the disks are created
             # all the disks must exist in the same zone 
-            - name: DISK_ZONES
+            - name: ZONES
               value: ''
 
             # set the label of the target disk volumes

charts/gcp/gcp-vm-disk-loss-by-label/experiment.yaml

@@ -61,7 +61,7 @@ spec:
 
     # set the zone in which all the disks are created
     # all the disks must exist in the same zone 
-    - name: DISK_ZONES
+    - name: ZONES
       value: ''
     
     # set the label of the target disk volumes

charts/gcp/gcp-vm-disk-loss/engine.yaml

@@ -32,7 +32,7 @@ spec:
             # set the disk zone(s) as comma seperated values in the corresponding 
             # order of DISK_VOLUME_NAME  
             # eg. zone1,zone2,...
-            - name: DISK_ZONES
+            - name: ZONES
               value: ''
 
             # parallel or serial; determines how chaos is injected

charts/gcp/gcp-vm-disk-loss/experiment.yaml

@@ -76,7 +76,7 @@ spec:
     # set the disk zone(s) as comma seperated values in the corresponding 
     # order of DISK_VOLUME_NAME  
     # eg. zone1,zone2,...
-    - name: DISK_ZONES
+    - name: ZONES
       value: ''
       
     labels:

charts/gcp/gcp-vm-instance-stop-by-label/engine.yaml

@@ -33,7 +33,7 @@ spec:
 
             # Zone in which the target vm instance(s) filtered by the label exist
             # all the instances should lie in a single zone
-            - name: INSTANCE_ZONES
+            - name: ZONES
               value: ''
 
             # enable it if the target instances are a part of a managed instance group

charts/gcp/gcp-vm-instance-stop-by-label/experiment.yaml

@@ -72,7 +72,7 @@ spec:
     
     # Zone in which the target vm instance(s) filtered by the label exist
     # all the instances should lie in a single zone
-    - name: INSTANCE_ZONES
+    - name: ZONES
       value: ''
     
     # enable it if the target instance is a part of a managed instance group

charts/gcp/gcp-vm-instance-stop/engine.yaml

@@ -30,7 +30,7 @@ spec:
             # 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
+            - name: ZONES
               value: ''
 
             # enable it if the target instance is a part of a managed instance group.

charts/gcp/gcp-vm-instance-stop/experiment.yaml

@@ -86,7 +86,7 @@ spec:
     # 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
+    - name: ZONES
       value: ''
       
     labels: