# KubeInvaders

</hp>

Chaos Container Definition

Load Test Code
Name
Programming Language

Project
Author
add an http endpoint to be analyzed during the chaos engineering session

Special Keys

h => Activate or deactivate help
s => Activate or deactivate shuffle for aliens
n => Change namespace
p => Activate or deactivate chaos engineering against pods
c => Activate or deactivate chaos engineering against nodes

##

Dear user, thank you for installing kubeinvaders!
This is a chaos engineering tool written by luckysideburn and friends from https://platformengineering.it for the community of kubernetes users, software developers, and admins.
It was born in 2019 as a gamified chaos engineering tool, and we are evolving it into a more serious instrument :d
here's how it works
For reports, bugs, ideas you can open issue on the project github repo https://github.com/lucky-sideburn/kubeinvaders or write to luckysideburn [at] gmail [dot] com
[[game mode button]]
Enabling the game console allows you to kill pods and launch workloads to stress cluster nodes (check "show keys and options" to understand how to do it). You can also jump between namespace and many other things.
[[add http check & chaos report checkbox]]
Use it to activate the monitoring of an ingress and generate real-time reporting. it's very useful to know what happens to your applications during chaos sessions. for now, we monitor the elapsed time of http calls and status codes. also, you have some very useful default metrics:
Selected namespace => indicates the current namespace focused on by the tool. you can jump between selected namespaces during installation.
>Deleted pods total => total number of killed pods.
Current chaos pods => when the node stress test mode is activated, this metric indicates the number of jobs stressing your cluster.
Current replicas state delay => a very important metric, indicates how long your cluster takes to return to the desired state that was before the chaos engineering session.
[[enable prog. mode button (under development)]]
Through yaml programming, you can define your own chaos engineering experiments and execute them. we have preloaded some presets for various open-source tools to stress test (this feature is still in development, so contributions are welcome).
Random Factor: 50
Add HTTP check & Chaos Report

##

h => Activate or deactivate help
s => Activate or deactivate shuffle for aliens
n => Change namespace
p => Activate or deactivate chaos engineering against pods
c => Activate or deactivate chaos engineering against nodes
Selected Namespace: NULL
Deleted Pods Total: 0
Chaos Jobs Total: 0
Current Chaos Pods: 0
Not Running Pods: 0
Current Replicas State Delay: 0 sec
Latest Replicas State Delay: 0 sec
Load Testing Presets & Chaos Programs
chaos-codename: CODENAME_PLACEHOLDER jobs: cpu-attack-job: additional-labels: chaos-controller: kubeinvaders chaos-type: stress-ng chaos-codename: CODENAME_PLACEHOLDER image: docker.io/luckysideburn/kubeinvaders-stress-ng:latest command: "stress-ng" args: - --version mem-attack-job: additional-labels: chaos-controller: kubeinvaders chaos-type: stress-ng chaos-codename: CODENAME_PLACEHOLDER image: docker.io/luckysideburn/kubeinvaders-stress-ng:latest command: "stress-ng" args: - --version experiments: - name: cpu-attack-exp job: cpu-attack-job loop: 5 - name: mem-attack-exp job: mem-attack-job loop: 5
test attack 1
test attack 2

PROJECT |
AUTHOR |
Chaos session date |
Chaos session time |
Checked URL |

HTTP Status Code
HTTP Elapsed (seconds)