A kubectl plugin for managing StellarNode resources in Kubernetes clusters.
cargo build --release --bin kubectl-stellar
cp target/release/kubectl-stellar ~/.local/bin/kubectl-stellar
chmod +x ~/.local/bin/kubectl-stellarkubectl krew install stellarList all StellarNode resources in the current namespace:
kubectl stellar listList all StellarNode resources across all namespaces:
kubectl stellar list --all-namespaces
# or
kubectl stellar list -AOutput in JSON or YAML format:
kubectl stellar list -o json
kubectl stellar list -o yamlGet logs from pods associated with a StellarNode:
kubectl stellar logs <node-name>Follow log output:
kubectl stellar logs <node-name> -fSpecify container name (if multiple containers):
kubectl stellar logs <node-name> -c <container-name>Show last N lines:
kubectl stellar logs <node-name> --tail 50Specify namespace:
kubectl stellar logs <node-name> -n <namespace>Check sync status of all StellarNode resources in the current namespace:
kubectl stellar status
# or
kubectl stellar sync-statusCheck status of a specific node:
kubectl stellar status <node-name>Check status across all namespaces:
kubectl stellar status -AOutput in JSON or YAML format:
kubectl stellar status -o json
kubectl stellar status -o yaml# List all nodes
kubectl stellar list
# Check if nodes are synced
kubectl stellar status
# View logs from a validator node
kubectl stellar logs my-validator -f
# Check status of a specific node in JSON format
kubectl stellar status my-horizon-node -o json- kubectl installed and configured
- Stellar-K8s operator installed in your cluster
- StellarNode CRD available
If you get "command not found" errors:
- Ensure the plugin is in your PATH
- The binary must be named
kubectl-stellar(orkubectl-stellar.exeon Windows) - The binary must be executable
If you get "No pods found" errors:
- Verify the StellarNode resource exists:
kubectl get stellarnodes - Check that pods are running:
kubectl get pods -l app.kubernetes.io/name=stellar-node - Ensure you're using the correct namespace