Installation Overview
KTube can be installed in several ways depending on your needs.
Installation Methods
CLI (Recommended)
Single binary with embedded Helm and Kind. Zero dependencies.
Helm Chart
Traditional Helm installation for advanced customization.
Manual (kubectl)
Direct manifest application for full control.
Comparison
| Method | Dependencies | Customization | Best For |
|---|---|---|---|
| CLI | None | Basic | Quick start, local dev |
| Helm | Helm CLI | Full | Production, CI/CD |
| kubectl | kubectl | Full | Air-gapped, auditing |
System Requirements
Kubernetes Cluster
- Kubernetes 1.25 or later
kubectlconfigured with cluster access- Cluster admin permissions (to install CRDs)
Local Development
If using the CLI to create a local cluster:
- Docker installed and running
- 4GB RAM available
- 20GB disk space
What Gets Installed?
| Component | Description | Namespace |
|---|---|---|
| ktube-operator | Controller that manages tunnel lifecycle | ktube-system |
| ktube-dashboard | Web UI for tunnel management | ktube-system |
| CRDs | Tunnel, TunnelProvider, TunnelBinding | cluster-wide |
| RBAC | ServiceAccount, ClusterRole | ktube-system |
Next Steps
Choose your installation method:
- CLI Installation - Recommended for most users
- Helm Installation - For production deployments