Krayne
CLI and SDK for creating, managing, and scaling Ray clusters on Kubernetes.
Krayne wraps the KubeRay operator behind a clean, opinionated interface so ML practitioners can get distributed compute without touching Kubernetes manifests.
A fast and intuitive terminal TUI (Terminal User Interface) is also available.
Navigate clusters, create with prefilled forms, scale, delete, and toggle tunnels — all with keyboard shortcuts. See the Interactive TUI guide for details.
Quickstart
pip install krayne
1. Connect Krayne to your Kubernetes cluster
krayne init picks a kubeconfig and context and saves them to ~/.krayne/config.yaml. Run it once after installing — every other command reads from that file.
krayne init
By default this prompts you to choose between ~/.kube/config, the local sandbox kubeconfig, and a custom path. To skip the prompts (e.g. in CI):
krayne init --kubeconfig ~/.kube/config --context my-context
Don't have a Kubernetes cluster handy? Run
krayne sandbox setupfirst to spin up a local k3s cluster with KubeRay pre-installed (Docker required).
2. Create a cluster
Pick whichever entrypoint suits you — they all produce the same Ray cluster. Pass -n/--namespace (or the namespace= field in ClusterConfig) to target a specific Kubernetes namespace; it defaults to default.
CLI:
krayne create my-cluster -n ml-team --gpus-per-worker 1 --workers 2
TUI — press c in the explorer to open the create form:
krayne tui
Python SDK:
from krayne.api import create_cluster
from krayne.config import ClusterConfig, WorkerGroupConfig
config = ClusterConfig(
name="my-cluster",
namespace="ml-team",
worker_groups=[WorkerGroupConfig(replicas=2, gpus=1)],
)
create_cluster(config, wait=True)
3. Run a Ray job against it
Recommended: krayne submit. It opens a tunnel if one isn't already up, then wraps ray job submit so your script's driver runs inside the cluster — no Python version match required, no ray.init glue:
krayne submit --cluster my-cluster -n ml-team -- python run.py
Add --no-wait to skip log tailing, or pass -- arg1 arg2 … to forward arguments to the script. See docs/reference/cli.md for the full reference.
Advanced: Ray Client (ray.init("ray://…")) — strict version match required
open_tunnel opens port-forward tunnels to the cluster's services so ray.init can reach the head node from your laptop, and closes them on exit:
import ray
from krayne.api import open_tunnel
with open_tunnel("my-cluster", "ml-team") as session:
ray.init(session.client_url) # ray://localhost:...
@ray.remote
def hello(i: int) -> str:
return f"Hello from worker {i}"
print(ray.get([hello.remote(i) for i in range(4)]))
ray.shutdown()
# tunnels closed when the block exits
When you're done, krayne delete my-cluster -n ml-team (or delete_cluster("my-cluster", "ml-team") from the SDK) tears the cluster down.
Interactive TUI
Krayne includes a k9s-style interactive terminal UI:
krayne tui
Or run it directly without installing: uvx krayne tui
Features
- Zero-config defaults — every command works with no flags. Sensible defaults get you a working cluster instantly.
- CLI and SDK — the CLI is a thin shell over the Python SDK. Anything you do from the terminal, you can do from code.
- Interactive TUI — k9s-style terminal UI for keyboard-driven cluster management.
- Functional API — stateless free functions, not class hierarchies. Easy to test, easy to compose.
- Pydantic config — validated configuration with YAML override support. No silent failures.
- Rich output — beautiful terminal tables via Rich, with
--output jsonfor scripting.
CLI Overview
krayne init Select kubeconfig + context (run once after install)
krayne create <name> Create a new Ray cluster
krayne get List clusters in a namespace
krayne describe <name> Show detailed cluster info
krayne scale <name> Scale a worker group
krayne delete <name> Delete a cluster
krayne tui Launch interactive TUI
All commands support -n/--namespace, --output json, and --debug flags.
Documentation
Full documentation is available at the Krayne docs site.
Requirements
- Python 3.10+
- A Kubernetes cluster with the KubeRay operator installed
- A valid kubeconfig (or running inside the cluster)
Development
# Clone and install
git clone https://github.com/roulbac/krayne.git
cd krayne
uv sync
# Run tests
uv run pytest
# Run integration tests (sandbox is provisioned automatically by test fixtures)
uv run pytest -m integration
Acknowledgements
Krayne is inspired by Spotify-Ray (sp-ray), Spotify's internal platform for running Ray on Kubernetes. The sp-ray team demonstrated that a CLI and SDK with sensible defaults, progressive disclosure of complexity, and managed KubeRay infrastructure can let ML practitioners focus on business logic instead of Kubernetes manifests. Krayne follows this philosophy as an open-source tool for the broader community.
License
Apache 2.0
Metadata
Release files for krayne 0.3.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| krayne-0.3.8.tar.gz | 64.1 kB | With provenance | Details for krayne-0.3.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| krayne-0.3.8-py3-none-any.whl | Python 3 | none | any | Details for krayne-0.3.8-py3-none-any.whl |
Total release size: 149.7 kB
Release files / krayne-0.3.8.tar.gz
| Download URL | krayne-0.3.8.tar.gz |
|---|---|
| Size | 64.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36e403102c5d1d6fedd036a55f4b679430c8e462507d16633fb13ce3a49dbf82
|
|
BLAKE2b-256 checksum How to use checksums |
74f0d8e54b26ec1cb6f58ef2fa671d82ab4e416e3edd03c5c19b58f7c330b414
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 29, 2026.
Transparency logRelease files / krayne-0.3.8-py3-none-any.whl
| Download URL | krayne-0.3.8-py3-none-any.whl |
|---|---|
| Size | 85.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3dbd48a241c77f466fd5acba67ca2fbe2cbe8d6523a590b175e7b8a7505b50a2
|
|
BLAKE2b-256 checksum How to use checksums |
7734cfb40978f6c6b9c36267aa08ad3bff2111660ad4f1e26bf1ac9e8eb19b5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 29, 2026.
Transparency logSecurity for krayne 0.3.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for krayne-0.3.8.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.