A Kubernetes controller for running Tor onion services, enabling anonymous web hosting within your cluster.
tor-controller is a Kubernetes operator that enables running Tor onion services within Kubernetes clusters. It solves the problem of exposing applications anonymously over the Tor network by providing native Kubernetes resource definitions for onion services, automating Tor daemon deployment and configuration.
Kubernetes administrators and developers who need to host privacy-focused applications or services that require anonymous access via the Tor network.
Developers choose tor-controller because it integrates Tor onion services directly into Kubernetes workflows, eliminating manual Tor configuration and providing declarative management of anonymous endpoints alongside other cluster resources.
Run Tor onion services on Kubernetes
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses Custom Resource Definitions (CRD) to define onion services via YAML manifests, allowing seamless management with kubectl and integration into existing K8s workflows, as shown in the README examples.
Supports both fixed .onion addresses via private key secrets and random addresses for ephemeral services, providing options for persistence or anonymity as needed, with clear YAML configuration.
Compatible with both v2 and v3 onion service protocols, with v3 as the default for modern security, and configurable via the spec.version field in manifests.
Designed to work with ingress controllers like nginx-ingress, enabling HTTP traffic routing over Tor, as demonstrated in the README with full deployment examples.
Uses v1alpha1 API version, which may lead to breaking changes and instability, making it risky for production environments without careful version management.
Fixed addresses require generating and managing private keys via secrets manually, adding operational overhead and security risks if not handled properly, as admitted in the README's key generation steps.
Inherits Tor's performance trade-offs, such as higher latency and lower throughput, which can impact applications sensitive to network speed or reliability.
Documentation is basic with few advanced examples, and there's no mention of community or third-party integrations, potentially hindering troubleshooting and scaling.