Disable arca config setup for hog scenarios (#239)

This is needed given the move to native krkn scenarios.

Signed-off-by: Naga Ravi Chaitanya Elluri <nelluri@redhat.com>

Author: chaitanyaenr

application-outages/run.sh

@@ -12,11 +12,7 @@ if [[ $KRKN_DEBUG == "True" ]];then
   ls -la /home/krkn/.kube
 fi
 
-
-
-
 checks
-config_setup
 
 # Substitute config with environment vars defined
 envsubst < /home/krkn/kraken/scenarios/app_outage.yaml.template > /home/krkn/kraken/scenarios/app_outage.yaml

common_run.sh

@@ -54,10 +54,3 @@ checks() {
   check_cluster_version
   set_kubernetes_platform
 }
-
-# Config substitutions
-config_setup(){
-  envsubst < /home/krkn/kraken/config/kube_burner.yaml.template > /home/krkn/kraken/config/kube_burner.yaml
-}
-
-

container-scenarios/run.sh

@@ -11,7 +11,6 @@ fi
 
 
 checks
-config_setup
 
 # Substitute config with environment vars defined
 envsubst < /home/krkn/kraken/scenarios/container_scenario.yaml.template > /home/krkn/kraken/scenarios/container_scenario.yaml

docs/node-io-hog.md

@@ -5,7 +5,7 @@ This scenario hogs the IO on the specified node on a Kubernetes/OpenShift cluste
 If enabling [Cerberus](https://github.com/krkn-chaos/krkn#kraken-scenario-passfail-criteria-and-report) to monitor the cluster and pass/fail the scenario post chaos, refer [docs](https://github.com/redhat-chaos/krkn-hub/tree/main/docs/cerberus.md). Make sure to start it before injecting the chaos and set `CERBERUS_ENABLED` environment variable for the chaos injection container to autoconnect.
 
 ```
-$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/root/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:node-io-hog
+$ podman run --name=<container_name> --net=host --env-host=true -v <path-to-kube-config>:/home/krkn/.kube/config:Z -d quay.io/krkn-chaos/krkn-hub:node-io-hog
 $ podman logs -f <container_name or container_id> # Streams Kraken logs
 $ podman inspect <container-name or container-id> --format "{{.State.ExitCode}}" # Outputs exit code which can considered as pass/fail for the scenario
 ```

network-chaos/run.sh

@@ -9,9 +9,7 @@ if [[ $KRKN_DEBUG == "True" ]];then
   ls -la /home/krkn/.kube
 fi
 
-
 checks
-config_setup
 
 # Substitute config with environment vars defined
 if [[ $TRAFFIC_TYPE == "egress" ]]; then

node-cpu-hog/run.sh

@@ -18,9 +18,8 @@ envsubst < $KRAKEN_FOLDER/scenarios/kube/cpu-hog.yml.template > $KRAKEN_FOLDER/s
 cat $KRAKEN_FOLDER/scenarios/kube/cpu-hog.yml
 # Substitute config with environment vars defined
 envsubst < $KRAKEN_FOLDER/config/config.yaml.template > $KRAKEN_FOLDER/config/cpu_config.yaml
-echo $KRAKEN_FOLDER
+
 checks
-config_setup
 
 # Run Kraken
 cd $KRAKEN_FOLDER

node-io-hog/run.sh

@@ -13,12 +13,11 @@ if [[ $KRKN_DEBUG == "True" ]];then
   set -ex
 fi
 
-
 envsubst < $KRAKEN_FOLDER/scenarios/kube/io-hog.yml.template > $KRAKEN_FOLDER/scenarios/kube/io-hog.yml
 # Substitute config with environment vars defined
 envsubst < $KRAKEN_FOLDER/config/config.yaml.template > $KRAKEN_FOLDER/config/io-config.yaml
+
 checks
-config_setup
 
 # Run Kraken
 cd $KRAKEN_FOLDER
@@ -29,5 +28,3 @@ if [[ $KRKN_DEBUG == "True" ]];then
 fi
 
 python3.9 run_kraken.py --config=config/io-config.yaml
-
-

node-memory-hog/run.sh

@@ -18,8 +18,6 @@ envsubst < $KRAKEN_FOLDER/scenarios/kube/memory-hog.yml.template > $KRAKEN_FOLDE
 envsubst < $KRAKEN_FOLDER/config/config.yaml.template > $KRAKEN_FOLDER/config/mem-config.yaml
 
 checks
-config_setup
-
 
 # Run Kraken
 cd $KRAKEN_FOLDER

pod-network-chaos/run.sh

@@ -10,7 +10,6 @@ if [[ $KRKN_DEBUG == "True" ]];then
 fi
 
 checks
-config_setup
 
 # Substitute config with environment vars defined
 envsubst < /home/krkn/kraken/scenarios/pod_network_scenario.yaml.template > /home/krkn/kraken/scenarios/pod_network_scenario.yaml

pod-scenarios/run.sh

@@ -10,7 +10,6 @@ if [[ $KRKN_DEBUG == "True" ]];then
 fi
 
 checks
-config_setup
 
 # Substitute config with environment vars defined
 if [[ -z "$POD_LABEL" ]]; then