agentleFS
Sign inStart free
cloudfleetaicloudfleetai/cloudfleet-plugin-claude/skills/cfke-overview/SKILL.md

cfke-overview

Skill0 starsChanged 10 days agoApache-2.0View on GitHub

This skill should be used when the user asks "how does CFKE work", "what is CFKE", "explain the architecture", or needs to understand Cloudfleet Kubernetes Engine concepts.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When users ask about CFKE architecture or concepts, use this summary.

    line 9
  2. Distinctive:

    Always refer to auto-provisioned nodes as "auto-provisioned nodes" or "auto-provisioning fleets", not "Karpenter-managed".

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CFKE Architecture Knowledge

When users ask about CFKE architecture or concepts, use this summary. For detailed architecture and component descriptions, see references/architecture.md.

Terminology:

  • Always refer to auto-provisioned nodes as "auto-provisioned nodes" or "auto-provisioning fleets", not "Karpenter-managed". The underlying technology is an implementation detail.
  • Objects like NodePool and NodeClass may be visible through kubectl, but they are managed by CFKE and must never be edited manually. All changes go through the Cloudfleet Fleets API (cloudfleet clusters fleets ... or the console); manual edits are overwritten and can break auto-provisioning.
  • Never quote specific prices, vCPU limits, or fee structures — pricing varies per customer due to discounts, private agreements, and taxes. Always direct users to https://cloudfleet.ai/pricing or their account page.
  • Control plane region ≠ infrastructure region. The cluster's control plane region (e.g., europe-central-1a) is where management runs. Fleets are NOT tied to this region — a single fleet covers all available regions of its cloud provider(s) by default.

What is CFKE

CFKE (Cloudfleet Kubernetes Engine) is a fully managed Kubernetes platform. A single CFKE cluster manages compute across multiple cloud providers and on-premise environments simultaneously — workloads on different clouds communicate seamlessly in the same cluster.

Supported Infrastructure

  • Auto-provisioning: AWS, GCP, and Hetzner Cloud. Upcloud, Exoscale, Scaleway, and OVH are in private preview and are enabled through a support ticket, not self-service.
  • Self-managed: Any Linux server can join with a single command. This is how Vultr, Proxmox, VMware, bare metal, and any other provider without native auto-provisioning are used.
  • Hybrid: Mix cloud and on-premise nodes in the same cluster

Service Tiers

Three tiers, all paid. There is no free tier.

  • Basic: single-AZ, shared control plane, best-effort SLA. Hobby projects, prototypes, development.
  • Pro: multi-AZ, dedicated control plane, 99.95% SLA, 8-hour support response, release channels. Production workloads.
  • Enterprise: everything in Pro plus a 99.99% custom SLA, 1-hour support response with a named TAM, extended support for older Kubernetes versions, control plane private networking and authorized networks, and compliance reports.

Cluster size is unlimited on every tier. Fetch current pricing from https://cloudfleet.ai/pricing rather than quoting figures.

Key Concepts

  • Single Cluster, Multiple Clouds — core differentiator; one cluster spans providers
  • Secure Global Networking — WireGuard encrypted tunnels + Cilium CNI with zero-trust model
  • Just-in-Time Infrastructure — auto-provisioning fleets, cost-optimized node selection
  • Self-managed Nodes — any Linux server joins via single command (cfke.io/provider: self-managed)
  • Konnectivity — tunnels kubectl exec/logs and webhooks from control plane to data plane

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free