From cloudfleet
This skill should be used when the user wants to create a CFKE cluster, set up fleets, connect cloud providers (AWS, GCP, Hetzner), add self-managed nodes, or get a new Cloudfleet environment running.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cloudfleet:cluster-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide users through the full process of getting a Cloudfleet cluster up and running — from creating the cluster through connecting cloud accounts to deploying a first workload. See [references/cluster-setup.md](references/cluster-setup.md) for detailed CLI commands and all provider examples.
Guide users through the full process of getting a Cloudfleet cluster up and running — from creating the cluster through connecting cloud accounts to deploying a first workload. See references/cluster-setup.md for detailed CLI commands and all provider examples.
First, fetch available options from the user's organization:
cloudfleet organization describe
This returns the available regions, versions, and cluster_tiers under the quota field. Use these values — do NOT hardcode regions or versions.
Note: The pro tier is only available after the user has entered a billing address and payment method in the Cloudfleet Console. If pro is not listed in quota.cluster_tiers, let the user know.
Then create the cluster:
cloudfleet clusters create <<EOF
{
"name": "<name>",
"tier": "<tier from quota.cluster_tiers>",
"region": "<region from quota.regions>",
"version_channel": "<version id from quota.versions>"
}
EOF
Control plane provisions in 2-3 minutes. The cluster starts with zero worker nodes — they provision on-demand when workloads are scheduled.
Important: The control plane region is where the management layer runs. It does NOT restrict where worker nodes can be provisioned — fleets cover all available regions of their cloud providers by default.
A fleet connects a cloud provider account so CFKE can auto-provision nodes. At least one provider must be configured for auto-provisioning to work.
Fleets are not region-scoped — a single Hetzner fleet can provision nodes in any Hetzner region (nbg1, fsn1, hel1, ash, sin, etc.). The same applies to AWS and GCP. Use node labels (topology.kubernetes.io/region) and placement constraints to control where workloads land.
cloudfleet clusters fleets create <cluster-id> <<EOF
{
"id": "my-fleet",
"hetzner": { "apiKey": "<hetzner-api-token>" },
"limits": { "cpu": 24 }
}
EOF
Supported providers: Hetzner (API token), AWS (IAM role ARN), GCP (project ID). A single fleet can span multiple providers. See references/cluster-setup.md for all provider examples.
Any Ubuntu 22.04/24.04 Linux server can join the cluster — bare metal, VMs, edge devices:
cloudfleet clusters add-self-managed-node <cluster-id> \
--host <ip-address> \
--region <datacenter-region> \
--zone <datacenter-zone>
For GPU nodes, add --install-nvidia-drivers.
cloudfleet clusters kubeconfig <cluster-id>
Deploy a test workload to trigger node provisioning:
kubectl create deployment nginx --image=nginx:latest --replicas=2
kubectl get pods -w
Pods transition Pending → ContainerCreating → Running as the auto-provisioner creates nodes. This confirms the full setup — cluster, fleet, and auto-provisioning — is working.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub cloudfleetai/cloudfleet-plugin-claude --plugin cloudfleet