Practical overview
When it fits
Use Kotal when blockchain or IPFS workloads need to be deployed through Kubernetes resources and managed by Kubernetes controllers, and a cluster with cert-manager is available.
Who it is for
- Infrastructure teams operating blockchain nodes or validators on Kubernetes.
- Teams managing IPFS peers, cluster peers or swarms in a Kubernetes environment.
Documented uses
- Deploy RPC, transaction, mining, archive, full or validator nodes for supported protocols.
- Create private Ethereum networks and Ethereum beacon or validation nodes.
- Deploy IPFS peers, cluster peers and swarms.
- Represent protocol-specific infrastructure as Kubernetes custom resources.
Requirements & limits
The project is published under the Apache-2.0 license. Use requires access to a Kubernetes cluster with cert-manager installed; the README recommends KinD for development.
- The README lists support for Bitcoin, Ethereum, Ethereum 2, NEAR, Polkadot, Chainlink, Filecoin, Stacks, Aptos, Graph and IPFS workloads.
- The listed protocol custom-resource APIs are marked alpha in the README.
- Kotal supports at least one client per listed protocol; Ethereum and Ethereum 2 have several named client options.
- The implementation is written in Go and distributed under Apache-2.0.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Submit the documented Ethereum node resource
Use Kotal’s README example to define and submit an Ethereum node configured with Besu, Goerli and HTTP RPC.
Before you start
- A Kubernetes cluster with cert-manager and Kotal installed
- kubectl access to the cluster
Steps
Save the README’s example as ethereum-node.yaml, with apiVersion ethereum.kotal.io/v1alpha1, kind Node, client besu, network goerli and rpc true.
Submit the resource with kubectl apply -f ethereum-node.yaml.
Expected outcome
The example Ethereum node resource is submitted to Kubernetes with the specified client, network and RPC setting.
Guide limitations
- The README provides a configuration and submission example, not a verified deployment result.
- The Ethereum custom-resource API is listed as alpha.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 15 October 2026
- Original website title
- kotalco/kotal · Official homepage title · retained in its source language

