Krkn-Chaos on Krkn

What is krkn-hub?

Mon, 01 Jan 0001 00:00:00 +0000

Hosts container images and wrapper for running scenarios supported by Krkn, a chaos testing tool for Kubernetes clusters to ensure it is resilient to failures. All we need to do is run the containers with the respective environment variables defined as supported by the scenarios without having to maintain and tweak files!

Getting Started

Checkout how to clone the repo and get started using this documentation page

Performance Dashboards

Mon, 01 Jan 0001 00:00:00 +0000

Performance dashboards

Krkn-chaos repository collection gives you a way to install a grafana on the cluster with dashboards loaded to help with monitoring the cluster for things like resource usage to find the outliers, API stats, Etcd health, Critical alerts etc. As well as specific metrics related to your krkn runs if elasticsearch is enabled.

https://github.com/krkn-chaos/visualize

git clone https://github.com/krkn-chaos/visualize
cd krkn-visualize

./deploy.sh 

OR 

./deploy.sh -c oc # openshift installation

The dashboards can be edited/modified to include your queries of interest by logging in as the admin user. New dasbhoards can be imported using the import script and following directions defined here

Chaos Recommendation Tool

Mon, 01 Jan 0001 00:00:00 +0000

This tool, designed for Kraken, operates through the command line and offers recommendations for chaos testing. It suggests probable chaos test cases that can disrupt application services by analyzing their behavior and assessing their susceptibility to specific fault types.

This tool profiles an application and gathers telemetry data such as CPU, Memory, and Network usage, analyzing it to suggest probable chaos scenarios. For optimal results, it is recommended to activate the utility while the application is under load.

Krkn Debugging Tips

Mon, 01 Jan 0001 00:00:00 +0000

Common Debugging Issues

SSL Certification

Error

...
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.***.io', port=6443): Max retries exceeded with url: /apis/config.openshift.io/v1/clusterversions (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1147)')))

Fix

The user needs to have tls verification by logging in using

$ oc login [-u=<username>] \
 [-p=<password>] \
 [-s=<server>] \
 [-n=<project>] \
 --insecure-skip-tls-verify

Also verify insecure-skip-tls-verify: true is in the kubeconfig:

Security self-assessment

Mon, 01 Jan 0001 00:00:00 +0000

Krkn Security Self-Assessment

Security reviewers: Tullio Sebastiani, Paige Patton, Naga Ravi Elluri

This document is intended to aid in roadmapping, and the onboarding of new maintainers.

Metadata


Software	https://github.com/krkn-chaos/krkn https://github.com/krkn-chaos/krkn-lib https://github.com/krkn-chaos/krkn-hub https://github.com/krkn-chaos/krknctl
Security Provider?	No. Krkn is designed to measure application or cluster resilience injecting controlled resource disruptions, but it should not be considered a security provider.
Languages	Python, Go, Bash
Software Bill of Materials	🔹 Krkn : https://github.com/krkn-chaos/krkn/releases/latest/download/sbom.json 🔹 krkn-lib : https://github.com/krkn-chaos/krkn-lib/releases/latest/download/sbom.json 🔹 krknctl : https://github.com/krkn-chaos/krknctl/releases/latest/download/sbom.json
Security Links	Known Weakness. Creation of a security-insights.yml should be added to the roadmap.

Overview

krkn is a chaos and resiliency testing tool for Kubernetes. Krkn injects deliberate failures into Kubernetes clusters to check if it is resilient to turbulent conditions.

Mon, 01 Jan 0001 00:00:00 +0000

ManagedCluster Scenarios

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.

Krkn-Chaos on Krkn

What is krkn-hub?

Getting Started

Performance Dashboards

Performance dashboards

Chaos Recommendation Tool

Krkn Debugging Tips

Common Debugging Issues

SSL Certification

Error

Fix

Security self-assessment

Krkn Security Self-Assessment

Table of Contents

Metadata

Overview

ManagedCluster Scenarios