We should look at using some leftover hardware to both look into container security and recoup some cost. A way to do that would be to combine these two projects:
We will call this the Rufus project. It'll work much like the current Geth project, with RPi nodes will answer to a Kubernetes orchestrator that will admin the containers on the nodes.
Very likely, we will spin these into their own subnet.
We should look at using some leftover hardware to both look into container security and recoup some cost. A way to do that would be to combine these two projects:
* https://autoize.com/mine-monero-docker/
* https://learn.networkchuck.com/courses/take/ad-free-youtube-videos/lessons/26093614-i-built-a-raspberry-pi-super-computer-ft-kubernetes-k3s-cluster-w-rancher
* https://learn.networkchuck.com/courses/take/ad-free-youtube-videos/lessons/29593608-cryptocurrency-mining-on-a-raspberry-pi-it-s-fun-trust-me#
We will call this the Rufus project. It'll work much like the current Geth project, with RPi nodes will answer to a Kubernetes orchestrator that will admin the containers on the nodes.
Very likely, we will spin these into their own subnet.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We should look at using some leftover hardware to both look into container security and recoup some cost. A way to do that would be to combine these two projects:
We will call this the Rufus project. It'll work much like the current Geth project, with RPi nodes will answer to a Kubernetes orchestrator that will admin the containers on the nodes.
Very likely, we will spin these into their own subnet.