mirror of
https://github.com/krkn-chaos/krkn.git
synced 2026-08-25 09:27:36 +00:00
This commit enables users to start Kraken to act as listener by setting the signal to PAUSE in the config to get the cluster to a desired test or run any setup before injecting chaos by setting the signal to RUN. This helps in cases where we have test cases that need to coordinate the chaos at a desired time depending on the state of the cluster/test run.
57 lines
4.3 KiB
YAML
57 lines
4.3 KiB
YAML
kraken:
|
|
distribution: openshift # Distribution can be kubernetes or openshift
|
|
kubeconfig_path: /root/.kube/config # Path to kubeconfig
|
|
exit_on_failure: False # Exit when a post action scenario fails
|
|
port: 8081
|
|
publish_kraken_status: True # Can be accessed at http://0.0.0.0:8081
|
|
signal_state: RUN # Will wait for the RUN signal when set to PAUSE before running the scenarios, refer docs/signal.md for more details
|
|
litmus_version: v1.10.0 # Litmus version to install
|
|
litmus_uninstall: False # If you want to uninstall litmus if failure
|
|
chaos_scenarios: # List of policies/chaos scenarios to load
|
|
- pod_scenarios: # List of chaos pod scenarios to load
|
|
- - scenarios/etcd.yml
|
|
- - scenarios/regex_openshift_pod_kill.yml
|
|
- scenarios/post_action_regex.py
|
|
- node_scenarios: # List of chaos node scenarios to load
|
|
- scenarios/node_scenarios_example.yml
|
|
- pod_scenarios:
|
|
- - scenarios/openshift-apiserver.yml
|
|
- - scenarios/openshift-kube-apiserver.yml
|
|
- time_scenarios: # List of chaos time scenarios to load
|
|
- scenarios/time_scenarios_example.yml
|
|
- litmus_scenarios: # List of litmus scenarios to load
|
|
- - https://hub.litmuschaos.io/api/chaos/1.10.0?file=charts/generic/node-cpu-hog/rbac.yaml
|
|
- scenarios/node_cpu_hog_engine.yaml
|
|
- cluster_shut_down_scenarios:
|
|
- - scenarios/cluster_shut_down_scenario.yml
|
|
- scenarios/post_action_shut_down.py
|
|
- namespace_scenarios:
|
|
- scenarios/regex_namespace.yaml
|
|
- scenarios/ingress_namespace.yaml
|
|
- zone_outages:
|
|
- scenarios/zone_outage.yaml
|
|
- application_outages:
|
|
- scenarios/app_outage.yaml
|
|
cerberus:
|
|
cerberus_enabled: True # Enable it when cerberus is previously installed
|
|
cerberus_url: http://0.0.0.0:8080 # When cerberus_enabled is set to True, provide the url where cerberus publishes go/no-go signal
|
|
check_applicaton_routes: False # When enabled will look for application unavailability using the routes specified in the cerberus config and fails the run
|
|
|
|
performance_monitoring:
|
|
deploy_dashboards: True # Install a mutable grafana and load the performance dashboards. Enable this only when running on OpenShift
|
|
repo: "https://github.com/cloud-bulldozer/performance-dashboards.git"
|
|
kube_burner_binary_url: "https://github.com/cloud-bulldozer/kube-burner/releases/download/v0.9.1/kube-burner-0.9.1-Linux-x86_64.tar.gz"
|
|
capture_metrics: True
|
|
config_path: config/kube_burner.yaml # Define the Elasticsearch url and index name in this config
|
|
metrics_profile_path: config/metrics-aggregated.yaml
|
|
prometheus_url: # The prometheus url/route is automatically obtained in case of OpenShift, please set it when the distribution is Kubernetes.
|
|
prometheus_bearer_token: # The bearer token is automatically obtained in case of OpenShift, please set it when the distribution is Kubernetes. This is needed to authenticate with prometheus.
|
|
uuid: # uuid for the run is generated by default if not set
|
|
enable_alerts: True # Runs the queries specified in the alert profile and displays the info or exits 1 when severity=error
|
|
alert_profile: config/alerts # Path to alert profile with the prometheus queries
|
|
|
|
tunings:
|
|
wait_duration: 60 # Duration to wait between each chaos scenario
|
|
iterations: 1 # Number of times to execute the scenarios
|
|
daemon_mode: False # Iterations are set to infinity which means that the kraken will cause chaos forever
|