From 8ea32a20e9ae8b6c7d7a34797628025ef1111f2e Mon Sep 17 00:00:00 2001 From: Tullio Sebastiani Date: Thu, 24 Oct 2024 11:50:41 +0200 Subject: [PATCH] fixed input_fields in Dockerfile (#216) Signed-off-by: Tullio Sebastiani --- application-outages/Dockerfile.template | 2 +- container-scenarios/Dockerfile.template | 2 +- network-chaos/Dockerfile.template | 2 +- node-cpu-hog/Dockerfile.template | 2 +- node-io-hog/Dockerfile.template | 2 +- node-memory-hog/Dockerfile.template | 2 +- node-scenarios/Dockerfile.template | 2 +- pod-network-chaos/Dockerfile.template | 2 +- pod-scenarios/Dockerfile.template | 2 +- power-outages/Dockerfile.template | 2 +- pvc-scenario/Dockerfile.template | 2 +- service-disruption-scenarios/Dockerfile.template | 2 +- service-hijacking/Dockerfile.template | 2 +- syn-flood/Dockerfile.template | 2 +- time-scenarios/Dockerfile.template | 2 +- zone-outages/Dockerfile.template | 2 +- 16 files changed, 16 insertions(+), 16 deletions(-) diff --git a/application-outages/Dockerfile.template b/application-outages/Dockerfile.template index 1efbd2a..3c16cf5 100644 --- a/application-outages/Dockerfile.template +++ b/application-outages/Dockerfile.template @@ -17,7 +17,7 @@ LABEL krknctl.kubeconfig_path="/home/krkn/.kube/config" LABEL krknctl.title="Application Outages" LABEL krknctl.description="Scenario to block the traffic ( Ingress/Egress ) of an application matching the labels for the specified duration of time to understand the behavior of the service/other services which depend on it during downtime. This helps with planning the requirements accordingly, be it improving the timeouts or tweaking the alerts etc." -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' diff --git a/container-scenarios/Dockerfile.template b/container-scenarios/Dockerfile.template index ee93654..a18fc73 100644 --- a/container-scenarios/Dockerfile.template +++ b/container-scenarios/Dockerfile.template @@ -18,6 +18,6 @@ LABEL krknctl.kubeconfig_path="/home/krkn/.kube/config" LABEL krknctl.title="Container Scenarios" LABEL krknctl.description="Scenario to block the traffic ( Ingress/Egress ) of an application matching the labels for the specified duration of time to understand the behavior of the service/other services which depend on it during downtime. This helps with planning the requirements accordingly, be it improving the timeouts or tweaking the alerts etc." -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/network-chaos/Dockerfile.template b/network-chaos/Dockerfile.template index 8ba94b3..3cc58f2 100644 --- a/network-chaos/Dockerfile.template +++ b/network-chaos/Dockerfile.template @@ -17,6 +17,6 @@ COPY network-chaos/network_chaos_ingress.yaml.template /home/krkn/kraken/scenari LABEL krknctl.kubeconfig_path="/home/krkn/.kube/config" LABEL krknctl.title="Network Chaos" LABEL krknctl.description="Scenario to introduce network latency, packet loss, and bandwidth restriction in the Node's host network interface. The purpose of this scenario is to observe faults caused by random variations in the network." -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/node-cpu-hog/Dockerfile.template b/node-cpu-hog/Dockerfile.template index c5b64a6..e693393 100644 --- a/node-cpu-hog/Dockerfile.template +++ b/node-cpu-hog/Dockerfile.template @@ -15,6 +15,6 @@ LABEL krknctl.kubeconfig_path="/home/krkn/.kube/config" LABEL krknctl.title="CPU Hog" LABEL krknctl.description="This scenario is based on the arcaflow arcaflow-plugin-stressng plugin. The purpose of this scenario is to create cpu pressure on a particular node of the Kubernetes/OpenShift cluster for a time span. To enable this plugin add the pointer to the scenario input file scenarios/arcaflow/cpu-hog/input.yaml as described in the Usage section. This scenario takes a list of objects named input_list" -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh \ No newline at end of file diff --git a/node-io-hog/Dockerfile.template b/node-io-hog/Dockerfile.template index f7a660a..3d7b415 100644 --- a/node-io-hog/Dockerfile.template +++ b/node-io-hog/Dockerfile.template @@ -17,7 +17,7 @@ LABEL krknctl.kubeconfig_path="/home/krkn/.kube/config" LABEL krknctl.title="I/O Hog" LABEL krknctl.description="This scenario is based on the arcaflow arcaflow-plugin-stressng plugin. The purpose of this scenario is to create disk pressure on a particular node of the Kubernetes/OpenShift cluster for a time span. The scenario allows to attach a node path to the pod as a hostPath volume." -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/node-memory-hog/Dockerfile.template b/node-memory-hog/Dockerfile.template index 9cc1360..62dadc8 100644 --- a/node-memory-hog/Dockerfile.template +++ b/node-memory-hog/Dockerfile.template @@ -18,6 +18,6 @@ LABEL krknctl.kubeconfig_path="/home/krkn/.kube/config" LABEL krknctl.title="Memory Hog" LABEL krknctl.description="This scenario is based on the arcaflow arcaflow-plugin-stressng plugin. The purpose of this scenario is to create Virtual Memory pressure on a particular node of the Kubernetes/OpenShift cluster for a time span." -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/node-scenarios/Dockerfile.template b/node-scenarios/Dockerfile.template index ca24fb8..35ae540 100644 --- a/node-scenarios/Dockerfile.template +++ b/node-scenarios/Dockerfile.template @@ -24,6 +24,6 @@ LABEL krknctl.title="Node scenarios" LABEL krknctl.description="This scenario disrupts the node(s) matching the label on a Kubernetes/OpenShift \ cluster. Actions/disruptions supported are listed. For further infos visit https://github.com/krkn-chaos/krkn/blob/main/docs/node_scenarios.md" -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/pod-network-chaos/Dockerfile.template b/pod-network-chaos/Dockerfile.template index b0d891e..1281524 100644 --- a/pod-network-chaos/Dockerfile.template +++ b/pod-network-chaos/Dockerfile.template @@ -21,7 +21,7 @@ accordingly, be it improving the timeouts or tweaking the alerts etc. With the c ports which are enabled by allowed network policy rule. This chaos scenario addresses this issue by using OVS flow rules to block ports related \ to the pod. It supports OpenShiftSDN and OVNKubernetes based networks." -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/pod-scenarios/Dockerfile.template b/pod-scenarios/Dockerfile.template index 189847b..5f47b6f 100644 --- a/pod-scenarios/Dockerfile.template +++ b/pod-scenarios/Dockerfile.template @@ -18,6 +18,6 @@ LABEL krknctl.kubeconfig="/home/krkn/.kube/config" LABEL krknctl.title="Pod Failures" LABEL krknctl.description="This scenario disrupts the pods matching the label in the specified namespace on a Kubernetes/OpenShift cluster." -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/power-outages/Dockerfile.template b/power-outages/Dockerfile.template index 410b299..34d5c4e 100644 --- a/power-outages/Dockerfile.template +++ b/power-outages/Dockerfile.template @@ -24,6 +24,6 @@ chaos scenario though, we figured this scenario was close to if the power went o our ec2 nodes would be stopped/powered off. We tried to look at if aws cli had a way to forcefully poweroff \ the nodes (not gracefully) and they don't currently support so this scenario is as close as we can get to \"pulling the plug\"" -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/pvc-scenario/Dockerfile.template b/pvc-scenario/Dockerfile.template index ee35551..167b413 100644 --- a/pvc-scenario/Dockerfile.template +++ b/pvc-scenario/Dockerfile.template @@ -19,6 +19,6 @@ LABEL krknctl.description="This scenario fills up a given PersistenVolumeClaim b The purpose of this scenario is to fill up a volume to understand faults cause by the application using this volume. \ For more information refer the following documentation (https://github.com/krkn-chaos/krkn/blob/main/docs/pvc_scenario.md)." -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/service-disruption-scenarios/Dockerfile.template b/service-disruption-scenarios/Dockerfile.template index c015954..2d397fa 100644 --- a/service-disruption-scenarios/Dockerfile.template +++ b/service-disruption-scenarios/Dockerfile.template @@ -19,6 +19,6 @@ LABEL krknctl.description="Using this type of scenario configuration one is able or a namespace matching a certain regex string. For more details documentation can be found here \ https://github.com/krkn-chaos/krkn/blob/main/docs/service_disruption_scenarios.md" -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/service-hijacking/Dockerfile.template b/service-hijacking/Dockerfile.template index 5f9c2fc..314161e 100644 --- a/service-hijacking/Dockerfile.template +++ b/service-hijacking/Dockerfile.template @@ -24,6 +24,6 @@ modifying the target Service selector to direct traffic to this web service for Please refer to the documentation for the scenario file syntax https://github.com/krkn-chaos/krkn/blob/main/docs/service_hijacking_scenarios.md" -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/syn-flood/Dockerfile.template b/syn-flood/Dockerfile.template index cabb40d..119b943 100644 --- a/syn-flood/Dockerfile.template +++ b/syn-flood/Dockerfile.template @@ -20,6 +20,6 @@ within the cluster or an external target reachable by the cluster. For more deta the following documentation (https://github.com/krkn-chaos/krkn-hub/blob/main/docs/syn-flood.md)." -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/time-scenarios/Dockerfile.template b/time-scenarios/Dockerfile.template index 49bbb80..0c4f84b 100644 --- a/time-scenarios/Dockerfile.template +++ b/time-scenarios/Dockerfile.template @@ -20,6 +20,6 @@ the label on a Kubernetes/OpenShift cluster. More information can be found here https://github.com/krkn-chaos/krkn/blob/master/docs/time_scenarios.md" -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh diff --git a/zone-outages/Dockerfile.template b/zone-outages/Dockerfile.template index c577af4..347860a 100644 --- a/zone-outages/Dockerfile.template +++ b/zone-outages/Dockerfile.template @@ -20,6 +20,6 @@ to understand the impact on both Kubernetes/OpenShift platforms control plane as nodes in that zone. More information is documented here https://github.com/krkn-chaos/krkn/blob/master/docs/zone_outage.md" -LABEL krknctl.inputFields='$KRKNCTL_INPUT' +LABEL krknctl.input_fields='$KRKNCTL_INPUT' ENTRYPOINT /home/krkn/run.sh