Scenarios on Krkn

Krkn-Hub All Scenarios Variables

Thu, 05 Jan 2017 00:00:00 +0000

These variables are to be used for the top level configuration template that are shared by all the scenarios in Krkn-hub.

Each section below corresponds to a section in the Krkn config reference. Set variables on the host running the container:

export <parameter_name>=<value>

Kraken

Signal and status publishing settings. See Kraken config for full details.

Parameter	Description	Default
`KRKN_KUBE_CONFIG`	Path to the kubeconfig file for cluster access	required
`PUBLISH_KRAKEN_STATUS`	Publish kraken status to the signal address	True
`SIGNAL_ADDRESS`	Address to publish kraken status to	0.0.0.0
`PORT`	Port to publish kraken status to	8081
`SIGNAL_STATE`	Waits for the RUN signal when set to PAUSE before running the scenarios, refer docs for more details	RUN

Cerberus

Cluster health monitoring integration. See Cerberus config for full details.

Krknctl All Scenarios Variables

Thu, 05 Jan 2017 00:00:00 +0000

These variables are to be used for the top level configuration template that are shared by all the scenarios in Krknctl.

Each section below corresponds to a section in the Krkn config reference. Pass flags when running a scenario:

krknctl run <scenario> --<parameter> <value>

Kraken

General run settings. See Kraken config for full details.

Supported Cloud Providers

Thu, 05 Jan 2017 00:00:00 +0000

AWS

NOTE: For clusters with AWS make sure AWS CLI is installed and properly configured using an AWS account. This should set a configuration file at $HOME/.aws/config for your the AWS account. If you have multiple profiles configured on AWS, you can change the profile by setting export AWS_DEFAULT_PROFILE=<profile-name>

export AWS_DEFAULT_REGION=<aws-region>

This configuration will work for self managed AWS, ROSA and Rosa-HCP

ManagedCluster Scenarios

Wed, 04 Jan 2017 00:00:00 +0000

ManagedCluster scenarios provide a way to integrate kraken with Open Cluster Management (OCM) and Red Hat Advanced Cluster Management for Kubernetes (ACM).

ManagedCluster scenarios leverage ManifestWorks to inject faults into the ManagedClusters.

The following ManagedCluster chaos scenarios are supported:

managedcluster_start_scenario: Scenario to start the ManagedCluster instance.
managedcluster_stop_scenario: Scenario to stop the ManagedCluster instance.
managedcluster_stop_start_scenario: Scenario to stop and then start the ManagedCluster instance.
start_klusterlet_scenario: Scenario to start the klusterlet of the ManagedCluster instance.
stop_klusterlet_scenario: Scenario to stop the klusterlet of the ManagedCluster instance.
stop_start_klusterlet_scenario: Scenario to stop and start the klusterlet of the ManagedCluster instance.

ManagedCluster scenarios can be injected by placing the ManagedCluster scenarios config files under managedcluster_scenarios option in the Kraken config. Refer to managedcluster_scenarios_example config file.