kraken: distribution: kubernetes # Distribution can be kubernetes or openshift kubeconfig_path: ~/.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 signal_address: 0.0.0.0 # Signal listening address chaos_scenarios: # List of policies/chaos scenarios to load - pod_disruption_scenarios: - scenarios/kube/pod.yml cerberus: cerberus_enabled: False # Enable it when cerberus is previously installed cerberus_url: # When cerberus_enabled is set to True, provide the url where cerberus publishes go/no-go signal check_application_routes: False # When enabled will look for application unavailability using the routes specified in the cerberus config and fails the run performance_monitoring: 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: False # Runs the queries specified in the alert profile and displays the info or exits 1 when severity=error alert_profile: config/alerts.yaml # Path to alert profile with the prometheus queries elastic: enable_elastic: False 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 telemetry: enabled: False # enable/disables the telemetry collection feature archive_path: /tmp # local path where the archive files will be temporarily stored events_backup: False # enables/disables cluster events collection logs_backup: False health_checks: # Utilizing health check endpoints to observe application behavior during chaos injection.