Eugenio Marzo 98766ffb58 create bundle
2021-01-03 11:55:38 +01:00
2021-01-02 18:40:55 +01:00
2019-03-29 11:14:41 +01:00
2020-05-28 06:30:43 +00:00
2020-05-24 08:28:44 +02:00
2021-01-02 18:35:13 +01:00
2021-01-03 11:55:38 +01:00
2021-01-03 10:49:01 +01:00
2020-12-26 12:44:43 +01:00
2021-01-03 11:55:38 +01:00
2021-01-03 08:56:52 +01:00
2019-10-25 16:35:08 -04:00
2020-12-26 12:44:43 +01:00
2019-10-27 09:54:51 +01:00
2019-04-21 22:02:31 +02:00
2019-04-21 23:29:46 +02:00
2019-03-31 11:55:28 +02:00
2019-10-31 11:36:48 +09:00
2021-01-03 10:49:01 +01:00
2021-01-03 08:54:04 +01:00
2021-01-02 18:35:13 +01:00
2019-09-13 09:57:49 +02:00
2019-03-31 11:55:28 +02:00
2019-04-21 23:31:07 +02:00
2020-05-24 08:39:01 +02:00
2021-01-03 10:46:22 +01:00
2020-12-26 12:44:43 +01:00
2021-01-02 18:35:13 +01:00
2020-12-26 22:54:11 +01:00
2020-12-26 22:54:11 +01:00

Alt Text

Gamified chaos engineering a analysis tool for Kubernetes. It is like Space Invaders but the aliens are PODs

Alt Text

Table of Contents

  1. Description
  2. Special Input Keys and features
  3. Installation
  4. Developing
  5. Configuration

Description

KubeInvaders has been developed using Defold.

Through KubeInvaders you can stress Kubernetes cluster in a fun way and check how it is resilient.

I added also new experimental features like a linter for the pods. The current latest image of the game include kube-linter developed by stackrox

Special Input Keys and features

Input Action
n Change namespace (you should define namespaces list. Ex: TARGET_NAMESPACE=foo1,foo2,foo3).
a Switch to automatic mode.
m Switch to manual mode.
h Show special keys.
q Hide help for special keys.
i Show pod's name. Move the ship towards an alien.
r Refresh log of a pod when spaceship is over the alien.
k Perform kube-linter analisys for a pod

Known problems

It seems that Kubeinvaders does not work with EKS because of problems with ServiceAccount. I cannot test it because EKS costs too much :D

Show logs of a pod

Move the spaceship over a white alien

Installation

Install with HELM

# Set target_namespace and ingress.hostname!
git clone https://github.com/lucky-sideburn/KubeInvaders.git

kubectl create namespace kubeinvaders

helm install kubeinvaders --set-string target_namespace="namespace1\,namespace2" \
--namespace kubeinvaders ./helm-charts/kubeinvaders \
--set ingress.hostName=kubeinvaders.io

Install client on your workstation

The easy way to install KubeInvaders is run it on you workstation but If you choose this method you cannot use kube-linter feature.

Create $HOME/.KubeInv.json like this:

{
  "token": ".....",
  "endpoint": "https://rancher.accolli.it:6443",
  "namespace": "namespace1,namespace2"
}

Install KubeInvaders on Openshift

To Install KubeInvaders on your Openshift Cluster clone this repo and launch the following commands:

oc create clusterrole kubeinvaders-role --verb=watch,get,delete,list --resource=pods,pods/log

TARGET_NAMESPACE=foobar,awesome-namespace
## You can define multiple namespaces ex: TARGET_NAMESPACE=foobar,foobar2

# Choose route host for your kubeinvaders instance.
ROUTE_HOST=kubeinvaders.org

# Please add your source ip IP_WHITELIST. This will add haproxy.router.openshift.io/ip_whitelist in KubeInvaders route
# https://docs.openshift.com/container-platform/3.9/architecture/networking/routes.html#whitelist
IP_WHITELIST="93.44.96.4"

oc new-project kubeinvaders --display-name='KubeInvaders'
oc create sa kubeinvaders -n kubeinvaders
oc adm policy add-cluster-role-to-user kubeinvaders-role -z kubeinvaders -n kubeinvaders

KUBEINVADERS_SECRET=$(oc get secret -n kubeinvaders --field-selector=type==kubernetes.io/service-account-token | grep 'kubeinvaders-token' | awk '{ print $1}' | head -n 1)

oc process -f openshift/KubeInvaders.yaml -p ROUTE_HOST=$ROUTE_HOST -p TARGET_NAMESPACE=$TARGET_NAMESPACE -p KUBEINVADERS_SECRET=$KUBEINVADERS_SECRET | oc create -f -

How the configuration of KubeInvaders DeploymentConfig should be (remember to use your TARGET_NAMESPACE and ROUTE_HOST)

Alt Text

Configuration

Environment Variables - Make the game more difficult to win!

Set the following variables in Kubernetes Deployment or Openshift DeploymentConfig

ENV Var Description
ALIENPROXIMITY (default 15) Reduce the value to increase distance between aliens
HITSLIMIT (default 0) Seconds of CPU time to wait before shooting
UPDATETIME (default 1) Seconds to wait before update PODs status (you can set also 0.x Es: 0.5)
Languages
JavaScript 39.1%
HTML 20.6%
Python 17.1%
Lua 15.8%
Shell 3.5%
Other 3.9%