Kraken app outage scenario fails to execute when pod-_selector is empty in the config file

[Noreen21]

2023-04-13 03:33:46,099 [INFO] Starting kraken 2023-04-13 03:33:46,105 [INFO] Initializing client to talk to the Kubernetes cluster 2023-04-13 03:33:47,424 [INFO] Publishing kraken status at http://0.0.0.0:8086 2023-04-13 03:33:47,425 [INFO] Publishing kraken status at http://0.0.0.0:8086 2023-04-13 03:33:47,426 [INFO] Starting http server at http://0.0.0.0:8086

2023-04-13 03:33:47,426 [INFO] Fetching cluster info 2023-04-13 03:33:47,437 [INFO] Error while reconciling 4.11.25: the cluster operator insights has not yet successfully rolled out
2023-04-13 03:33:47,437 [INFO] Server URL: https://api.e28-h35-r750.example.com:6443 2023-04-13 03:33:47,437 [INFO] Generated a uuid for the run: e1de432b-94b8-4f75-9b38-edde838ddb2d 2023-04-13 03:33:47,437 [INFO] Daemon mode not enabled, will run through 1 iterations

2023-04-13 03:33:47,437 [INFO] Executing scenarios for iteration 0 2023-04-13 03:33:47,437 [INFO] connection set up 2023-04-13 03:33:47,438 [INFO] response RUN 2023-04-13 03:33:47,438 [INFO] Injecting application outage 2023-04-13 03:33:47,441 [INFO] Creating the network policy 2023-04-13 03:33:47,510 [ERROR] Failed to run kubectl create -f kraken_network_policy.yaml -n boatload-1 --validate=false, error: Command 'kubectl create -f kraken_network_policy.yaml -n boatload-1 --validate=false' returned non-zero exit status 1.

Config file:

application_outage:                                  # Scenario to create an outage of an application by blocking traffic
  duration: 30                                      # Duration in seconds after which the routes will be accessible
  namespace: boatload-1            # Namespace to target - all application routes will go inaccessible if pod selector is empty
  pod_selector:                           # Pods to target
  block: [Ingress, Egress]                           # It can be Ingress or Egress or Ingress, Egress