Rancher is a comprehensive Kubernetes management platform that provides multi-cluster management, authentication/authorization, application catalog (Helm charts), fleet management, and a web UI. The codebase is a monolithic Go application with two primary entry points: the Rancher server (main.go) and the Rancher agent (cmd/agent/main.go). The server runs as a Kubernetes operator using the controller-runtime pattern, managing custom resources for clusters, projects, users, authentication providers, and catalogs. It integrates with upstream Kubernetes APIs via generated clients (norman, wrangler) and provides a unified API (Steve) for downstream cluster management. The architecture follows a hub-and-spoke model where the Rancher server manages multiple downstream clusters through cluster agents. Key data flows include: cluster provisioning (RKE2, K3s, cloud providers), authentication (OIDC, LDAP, AD, SAML), catalog synchronization (Helm charts from Git/OCI), and fleet-based GitOps deployment. External dependencies include Kubernetes (v1.36), etcd, cert-manager, and various cloud provider SDKs (AWS, Azure, GCP, AliCloud). The codebase demonstrates high craftsmanship with extensive code generation, clean separation of concerns, comprehensive test infrastructure (unit, integration, controller-runtime envtest), and production-grade operational tooling.
This repository is a retired reference implementation for deploying AI coding agents (CLAWDINATORs) on AWS using NixOS. It provides a complete image-based provisioning pipeline: NixOS images are built with nixos-generators, uploaded to S3, imported as AMIs, and launched as EC2 instances via OpenTofu. The agents run the openclaw gateway, connecting to Discord and GitHub to monitor repositories and assist maintainers. The system includes shared memory via EFS, a control plane Lambda for fleet management, GitHub App token refresh, and scheduled GitHub state sync. The codebase is well-structured with a modular NixOS module, clean shell scripts, and proper infrastructure-as-code patterns. However, the project is explicitly retired (fleet decommissioned August 2026, workflows disabled), so it serves primarily as a historical reference and learning resource for NixOS-on-AWS deployment patterns.