ITT anonymous access to eom.dev services using Tor is documented and discussed. Deployment details and onion addresses are enumerated here. The scope of this thread should be limited to the implementation details of Tor on eom.dev.
Kubernetes Ingress Controllers and Tor Hidden Services
The Tor Browser allows users to access online services anonymously by routing internet traffic through encrypted tunnels between multiple nodes around the world. While Tor can access websites on the standard clearnet, doing so requires the use of public exit nodes, which can be logged and monitored by third parties. By deploying dedicated .onion addresses for the services available on eom.dev, Tor users can access them even more securely without leaving the Tor network through one such exit node.
Deployment
Hidden services in Kubernetes are created using bugfest/tor-controller, which functions similar to an ingress controller:
The Tor controller was deployed to the eom.dev cluster using the following Ansible role:
eom.dev
The following .onion addresses can be used to access eom.dev services on the Tor network: