[Sandbox] Kubeinvaders

[lucky-sideburn]

Application contact emails

[email protected]

Project Summary

Chaos Engineering tool for Kubernetes

Project Description

Kubeinvaders is a Kubernetes chaos engineering tool created in 2019 as a fun side project.
Its primary function is to kill pods and stress worker nodes through an interface reminiscent of the Space Invaders game. We've added various custom features, including graphs for monitoring HTTP ingress during chaos sessions and the ability to schedule experiments.

The software is licensed under Apache 2.0, and the technology stack is very simple. We use OpenResty as a web server, Python and Lua for backend logic, and plain JavaScript and HTML for the frontend.

Org repo URL (provide if all repos under the org are in scope of the application)

N/A

Project repo URL in scope of application

https://github.com/lucky-sideburn/kubeinvaders

Additional repos in scope of the application

No response

Website URL

https://platformengineering.it/

Roadmap

https://github.com/lucky-sideburn/kubeinvaders/blob/master/README.md#roadmap

Roadmap context

The roadmap focuses on developing a fully open-source platform, primarily intended for SRE teams, to provide a comprehensive overview of projects and namespaces where chaos engineering sessions have been conducted over time. Statistics on chaos engineering usage and service uptime reports should offer insights into areas where improvements can be made to enhance system robustness.

At platformengineering.it, we intend to provide the project under the Apache 2.0 license, while offering support to clients and partners for usage and more advanced reporting.

Contributing Guide

https://github.com/lucky-sideburn/kubeinvaders/blob/master/CONTRIBUTING.md

Code of Conduct (CoC)

https://github.com/lucky-sideburn/kubeinvaders/blob/master/CODE_OF_CONDUCT.md

Adopters

No response

Contributing or Sponsoring Org

No response

Maintainers file

https://github.com/lucky-sideburn

IP Policy

• If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

• If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?

The CNCF's vast network of developers, users, and organizations will significantly increase Kubeinvaders' exposure. This will attract new contributors, users, and potential collaborators, fostering a more vibrant and diverse community.

Benefit to the Landscape

We think adding a bit of fun with a game-like project could be a great way to get new developers interested.

Cloud Native 'Fit'

No response

Cloud Native 'Integration'

No response

Cloud Native Overlap

No response

Similar projects

N/A

Landscape

yes

Business Product or Service to Project separation

N/A

Project presentations

No response

Project champions

No response

Additional information

No response

[lucky-sideburn]

Hi @angellk

Could I ask as what was the outcome of the review session on October 8?

Thanks :)

[angellk]

hi @lucky-sideburn - your project has not come up yet for TOC review. Please see the project board for where Kubeinvaders is at in the queue.

[mrbobbytables]

@TheFoxAtWork will follow up

[TheFoxAtWork]

Kubeinvaders - the TOC has determined the project is not quite viable for our matriculation process, but we do see the value in Kubeinvaders as an educational tool. It is our recommendation that the project engage Litmus and other chaos engineering projects in the ecosystem for potentially being included, or to re-apply in 6 months with a name change (refer to the recent naming guidance)

[lucky-sideburn]

Dear @TheFoxAtWork and CNCF,

Thank you very much for your feedback; it is very important to me. Reading that there is value in my open-source project means more to me than having completed 100 projects successfully in an enterprise and work context. :D

No problem at all about my application not being accepted; I totally understand the reasons. It was very interesting to read your suggestion—I had never thought that the project could be an educational tool for Kubernetes and chaos engineering. In fact, it is currently being used by some important companies to train people in the observability area.

As for the name, I totally agree (it will be difficult to choose a new one, but I will give it a try! :) )