Geth is a collective ecosystem for aggregating compute across many cheap nodes for small tasks.

Thanks to NetworkChuck's [tutorial](https://www.youtube.com/watch?v=X9fSMGkjtug) for helping to get this started and the Antsle nano models for the hardware to run this.

# Etymology

The [Geth](http://masseffect.wikia.com/wiki/Geth) are a fictional race in the Mass Effect universe. Geth are individual processes running on many platforms. The more devices, the smarter the collective or gestalt consciousness of the entity becomes.

# Relevant Files and Software

This is a Rancher orchestration of Kubernetes. This allows us to centrally manage a lot of small processes, such as CTF images, without the weight of managing full virtual machines.

Note: containers make it easier to isolate dependencies, especially for less-maintained apps or when we want to set up an isolated network ecosystem. However, they do introduce performance overhead. This is helpful for micro-services, but it's not helpful for heavy, oft-used or data-intensive applications. Some articles with tracking on the wasted compute using containers are below.
* https://pythonspeed.com/articles/docker-performance-overhead/
* https://www.torizon.io/blog/containers-in-linux-and-performance-impact

# Available Clients
This system does not have a client itself, but the containers managed in it may provide SSH or Web clients.

# Equivalents or Competition

There are many ways to run containers other than Rancher/k3s:
* Self-hosted: RedHat OpenShift, [Antsle antMan](https://antsle.com), and raw Docker
* Cloud: [Containers on Azure](https://azure.microsoft.com/en-us/products/category/containers/), [AWS Containers](https://aws.amazon.com/containers/)