mirror of
https://github.com/krkn-chaos/krkn.git
synced 2026-08-25 09:27:36 +00:00
Setting config back to all scenarios running
Functional & Unit Tests / Functional & Unit Tests (push) Failing after 9m4s
Functional & Unit Tests / Generate Coverage Badge (push) Has been skipped
Functional & Unit Tests / Functional & Unit Tests (push) Failing after 9m4s
Functional & Unit Tests / Generate Coverage Badge (push) Has been skipped
Signed-off-by: Paige Patton <prubenda@redhat.com>
This commit is contained in:
committed by
Naga Ravi Chaitanya Elluri
parent
97f4c1fd9c
commit
b801308d4a
+44
-44
@@ -1,5 +1,5 @@
|
||||
kraken:
|
||||
kubeconfig_path: ~/Scrap/maybank-cluster/auth/kubeconfig # Path to kubeconfig
|
||||
kubeconfig_path: ~/.kube/config # Path to kubeconfig
|
||||
exit_on_failure: False # Exit when a post action scenario fails
|
||||
auto_rollback: True # Enable auto rollback for scenarios.
|
||||
rollback_versions_directory: /tmp/kraken-rollback # Directory to store rollback version files.
|
||||
@@ -8,50 +8,50 @@ kraken:
|
||||
signal_address: 0.0.0.0 # Signal listening address
|
||||
port: 8081 # Signal port
|
||||
chaos_scenarios:
|
||||
# # List of policies/chaos scenarios to load
|
||||
# - hog_scenarios:
|
||||
# - scenarios/kube/cpu-hog.yml
|
||||
# - scenarios/kube/memory-hog.yml
|
||||
# - scenarios/kube/io-hog.yml
|
||||
# - application_outages_scenarios:
|
||||
# - scenarios/openshift/app_outage.yaml
|
||||
# - container_scenarios: # List of chaos pod scenarios to load
|
||||
# - scenarios/openshift/container_etcd.yml
|
||||
# - pod_network_scenarios:
|
||||
# - scenarios/openshift/network_chaos_ingress.yml
|
||||
# - scenarios/openshift/pod_network_outage.yml
|
||||
# - pod_disruption_scenarios:
|
||||
# - scenarios/openshift/etcd.yml
|
||||
# - scenarios/openshift/regex_openshift_pod_kill.yml
|
||||
# - scenarios/openshift/prom_kill.yml
|
||||
# - scenarios/openshift/openshift-apiserver.yml
|
||||
# - scenarios/openshift/openshift-kube-apiserver.yml
|
||||
# - node_scenarios: # List of chaos node scenarios to load
|
||||
# - scenarios/openshift/aws_node_scenarios.yml
|
||||
# - scenarios/openshift/vmware_node_scenarios.yml
|
||||
# - scenarios/openshift/ibmcloud_node_scenarios.yml
|
||||
# - time_scenarios: # List of chaos time scenarios to load
|
||||
# - scenarios/openshift/time_scenarios_example.yml
|
||||
# - cluster_shut_down_scenarios:
|
||||
# - scenarios/openshift/cluster_shut_down_scenario.yml
|
||||
# - service_disruption_scenarios:
|
||||
# - scenarios/openshift/regex_namespace.yaml
|
||||
# - scenarios/openshift/ingress_namespace.yaml
|
||||
# - zone_outages_scenarios:
|
||||
# - scenarios/openshift/zone_outage.yaml
|
||||
# - pvc_scenarios:
|
||||
# - scenarios/openshift/pvc_scenario.yaml
|
||||
# - network_chaos_scenarios:
|
||||
# - scenarios/openshift/network_chaos.yaml
|
||||
# - service_hijacking_scenarios:
|
||||
# - scenarios/kube/service_hijacking.yaml
|
||||
# - syn_flood_scenarios:
|
||||
# - scenarios/kube/syn_flood.yaml
|
||||
- network_chaos_ng_scenarios:
|
||||
# List of policies/chaos scenarios to load
|
||||
- hog_scenarios:
|
||||
- scenarios/kube/cpu-hog.yml
|
||||
- scenarios/kube/memory-hog.yml
|
||||
- scenarios/kube/io-hog.yml
|
||||
- application_outages_scenarios:
|
||||
- scenarios/openshift/app_outage.yaml
|
||||
- container_scenarios: # List of chaos pod scenarios to load
|
||||
- scenarios/openshift/container_etcd.yml
|
||||
- pod_network_scenarios:
|
||||
- scenarios/openshift/network_chaos_ingress.yml
|
||||
- scenarios/openshift/pod_network_outage.yml
|
||||
- pod_disruption_scenarios:
|
||||
- scenarios/openshift/etcd.yml
|
||||
- scenarios/openshift/regex_openshift_pod_kill.yml
|
||||
- scenarios/openshift/prom_kill.yml
|
||||
- scenarios/openshift/openshift-apiserver.yml
|
||||
- scenarios/openshift/openshift-kube-apiserver.yml
|
||||
- node_scenarios: # List of chaos node scenarios to load
|
||||
- scenarios/openshift/aws_node_scenarios.yml
|
||||
- scenarios/openshift/vmware_node_scenarios.yml
|
||||
- scenarios/openshift/ibmcloud_node_scenarios.yml
|
||||
- time_scenarios: # List of chaos time scenarios to load
|
||||
- scenarios/openshift/time_scenarios_example.yml
|
||||
- cluster_shut_down_scenarios:
|
||||
- scenarios/openshift/cluster_shut_down_scenario.yml
|
||||
- service_disruption_scenarios:
|
||||
- scenarios/openshift/regex_namespace.yaml
|
||||
- scenarios/openshift/ingress_namespace.yaml
|
||||
- zone_outages_scenarios:
|
||||
- scenarios/openshift/zone_outage.yaml
|
||||
- pvc_scenarios:
|
||||
- scenarios/openshift/pvc_scenario.yaml
|
||||
- network_chaos_scenarios:
|
||||
- scenarios/openshift/network_chaos.yaml
|
||||
- service_hijacking_scenarios:
|
||||
- scenarios/kube/service_hijacking.yaml
|
||||
- syn_flood_scenarios:
|
||||
- scenarios/kube/syn_flood.yaml
|
||||
- network_chaos_ng_scenarios:
|
||||
- scenarios/kube/pod-network-filter.yml
|
||||
# - scenarios/kube/node-network-filter.yml
|
||||
# - kubevirt_vm_outage:
|
||||
# - scenarios/kubevirt/kubevirt-vm-outage.yaml
|
||||
- scenarios/kube/node-network-filter.yml
|
||||
- kubevirt_vm_outage:
|
||||
- scenarios/kubevirt/kubevirt-vm-outage.yaml
|
||||
|
||||
cerberus:
|
||||
cerberus_enabled: False # Enable it when cerberus is previously installed
|
||||
|
||||
Reference in New Issue
Block a user