Skip to content
This repository has been archived by the owner on Sep 7, 2021. It is now read-only.

Script to check Kubernetes nodes on stress (CPU/RAM) resistance.

License

Notifications You must be signed in to change notification settings

druesendieb/kube-stresscheck

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

kube-stresscheck

Script to check Kubernetes nodes on stress (CPU/RAM) resistance.

It will run 5 iterations of stress command with following parameters:

  • CPU forks equal to number of cores.
  • Memory forks will be computed to allocate whole memory.

For details what stress does under the hood see manual.

Quick start

kubectl apply -f https://raw.githubusercontent.com/giantswarm/kube-stresscheck/master/examples/node.yaml

Wait at least 30 seconds and check for CrashLooping pods and NotReady nodes.

kubectl get pods -n kube-system
kubectl get nodes
kubectl delete -f https://raw.githubusercontent.com/giantswarm/kube-stresscheck/master/examples/node.yaml

Usually pods like kube-proxy, nginx-ingress-controller, calico-node are crashlooping. If kubelet or docker was affected by stress test then node will become NotReady.

Stress test whole cluster

If you're really brave, then you can start stress check on the whole cluster (including a master node).

kubectl apply -f https://raw.githubusercontent.com/giantswarm/kube-stresscheck/master/examples/cluster.yaml

Most probably you have just KILLED your cluster. It will probably require manual intervention after this command.

If cluster is still ok, then remove stress check.

kubectl delete -f https://raw.githubusercontent.com/giantswarm/kube-stresscheck/master/examples/node.yaml

About

Script to check Kubernetes nodes on stress (CPU/RAM) resistance.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Go 82.3%
  • Dockerfile 17.7%