Install FissionPlane on Kubernetes with a Helm Chart

​

Prerequisites

• Kubernetes 1.28 or later. FissionPlane is tested against the three most recent minor releases.
• Helm 3. The chart uses Helm 3 features and is not compatible with Helm 2.
• A node pool with KVM support. Firecracker requires hardware virtualization. Each node in the sandbox pool must expose /dev/kvm. Verify this by running ls /dev/kvm on a candidate node.
• Object storage for snapshots. Sandbox pause/resume writes memory snapshots to an S3-compatible bucket or blob store. You’ll configure the storage credentials during the Helm install.

​

Supported platforms

​

Node pool requirements

• Each node must expose /dev/kvm (hardware or nested virtualization enabled at the hypervisor).
• Apply the taint fissionplane.dev/sandbox=true:NoSchedule to sandbox nodes so only FissionPlane workloads are scheduled there.
• Size the pool based on your expected concurrent sandbox count. Each Firecracker microVM reserves its own CPU and memory.

# Verify KVM is available on a node (run on the node itself)
ls /dev/kvm

# Taint your sandbox node pool (example — adjust node-pool label as needed)
kubectl taint nodes -l fissionplane.dev/role=sandbox \
  fissionplane.dev/sandbox=true:NoSchedule

​

Install with Helm

helm repo add fissionplane https://charts.fissionplane.dev

helm repo update

helm install fissionplane fissionplane/fissionplane \
  --namespace fissionplane \
  --create-namespace \
  --set controlPlane.apiKey=<your-key>

kubectl get pods -n fissionplane

NAME                                      READY   STATUS    RESTARTS   AGE
fissionplane-control-plane-7d9f6b-xk2p9   1/1     Running   0          2m
fissionplane-gateway-5c8b4d-rtn7q          1/1     Running   0          2m
fissionplane-node-runtime-ds-6hj2k         1/1     Running   0          2m

kubectl get service -n fissionplane

NAME                     TYPE           CLUSTER-IP     EXTERNAL-IP       PORT(S)
fissionplane-gateway     LoadBalancer   10.96.14.201   203.0.113.42      443:30443/TCP

​

Air-gapped installs

# Override the registry during install
helm install fissionplane fissionplane/fissionplane \
  --namespace fissionplane \
  --create-namespace \
  --set controlPlane.apiKey=<your-key> \
  --set image.registry=registry.internal.example.com

​

Configure the SDK after install

export FISSIONPLANE_API_URL="https://<your-control-plane-url>"
export FISSIONPLANE_API_KEY="<your-key>"

import { FissionPlane } from '@fissionplane/sdk'

const client = new FissionPlane()
const sandbox = await client.sandboxes.create({ template: 'base' })
console.log('Connected. Sandbox ID:', sandbox.sandboxId)
await sandbox.delete()

from fissionplane import FissionPlane

client = FissionPlane()
sandbox = client.sandboxes.create("base")
print("Connected. Sandbox ID:", sandbox.sandbox_id)
sandbox.delete()

use fissionplane::{ClientOptions, FissionPlane};
use fissionplane::models::CreateSandboxRequest;

let client = FissionPlane::new(ClientOptions::new())?;
let sandbox = client.sandboxes().create(
    CreateSandboxRequest { template: "base".to_owned(), ..Default::default() },
    None,
).await?;
println!("Connected. Sandbox ID: {}", sandbox.info.sandbox_id);
sandbox.delete().await?;