A Kubernetes operator for deploying and managing highly-available Cosmos SDK blockchain nodes and supporting chains like Penumbra.
Cosmos Operator is a Kubernetes Operator that automates the deployment and management of blockchain nodes built with the Cosmos SDK and other CometBFT-based chains like Penumbra. It provides Custom Resource Definitions (CRDs) to define node configurations as YAML files, enabling highly-available, fault-tolerant infrastructure with minimal manual oversight. The tool solves the complexity of manually orchestrating blockchain nodes in Kubernetes by applying the operator pattern to capture domain-specific operational knowledge.
DevOps engineers, SREs, and blockchain infrastructure teams who manage Cosmos SDK-based blockchain nodes in Kubernetes environments and want to automate node lifecycle management. It's also for organizations running validator sentries, RPC nodes, or seed nodes that require production-grade reliability and scalability.
Developers choose Cosmos Operator because it provides a specialized, production-tested solution for Cosmos ecosystem nodes, going beyond generic Kubernetes StatefulSets by offering chain-specific features like scheduled upgrades, automatic PVC resizing, and support for validator sentry configurations. Its deep integration with Cosmos SDK conventions and support for tools like horcrux and heighliner images reduces operational overhead compared to manual or generic orchestration approaches.
Cosmos Operator is a kubernetes operator for managing cosmos nodes
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Used in production by Strangelove for over a year, with features like scheduled upgrades and automatic PVC resizing, ensuring reliability for Cosmos nodes.
Designed specifically for Cosmos SDK and CometBFT chains, offering CRDs like CosmosFullNode for RPC nodes, validator sentries, and seed nodes with persistent peer support.
Goes beyond StatefulSets with features like automatic PVC expansion at storage thresholds and safe, periodic VolumeSnapshots for backups, reducing manual intervention.
Provides highly-available configurations and quicker p2p discovery via private peers, enhancing node reliability and network connectivity.
Requires heighliner images and specific uid:gid settings; validator sentries need horcrux for remote signing, adding complexity and vendor lock-in.
Tested primarily on GKE and bare-metal, with no guaranteed support for other Kubernetes providers, and may not work for all Cosmos chains due to convention divergences.
Roadmap items like HPA support, automatic upgrades via governance, and corrupt data recovery are not yet implemented, limiting scalability and self-healing capabilities.