kubesphere-fluid
KubeSphere Fluid management Skill. Use when user asks to install or enable Fluid, check Fluid status, view Fluid pods/logs/CRDs, create or update Dataset, AlluxioRuntime, JuiceFSRuntime, or ThinRuntime, perform DataLoad or cache warming, scale runtime, or troubleshoot Fluid issues in KubeSphere.
npx skills add kubesphere/kubesphere --skill kubesphere-fluid --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides the agent to manage the full Fluid lifecycle in KubeSphere: install/upgrade Fluid via InstallPlan, check status and CRDs, generate Dataset manifests with mounts, generate AlluxioRuntime, JuiceFSRuntime, or ThinRuntime manifests for caching, perform DataLoad for cache warming, scale runtimes, uninstall, and troubleshoot Fluid Pods, CRDs, and mount issues.
How it works
- Verifies extension name and version before creating an InstallPlan, defaults extension name to fluid when not exposed otherwise.
- Prefers executable outputs: InstallPlan YAML, Dataset YAML, AlluxioRuntime YAML, kubectl commands, or a short ordered procedure.
- Before Dataset/Runtime generation, checks API versions with:
kubectl api-resources --api-group data.fluid.io - For creating resources, uses required parameter handling: name, namespace, mountPoint, replicas, quota, mediumType, path must reflect user-provided values exactly as specified.
- Output scope rules:
- Create Dataset → only Dataset YAML
- Create AlluxioRuntime → only AlluxioRuntime YAML
- Create JuiceFSRuntime → only JuiceFSRuntime YAML
- Create ThinRuntime → only ThinRuntime YAML
- Create Dataset with Runtime → both Dataset and respective Runtime YAML
- Create DataLoad → only DataLoad YAML
- Provides three query approaches: KubeSphere API, kubectl, ksctl; lists supported resource types and example commands.
- Warns about uninstall effects on CRDs/CRs whenever applicable.
When to use it
Use when the user asks to install/enable Fluid, check status, view pods/logs/CRDs, create/update Dataset or any of AlluxioRuntime / JuiceFSRuntime / ThinRuntime, perform DataLoad or cache warming, scale runtime, or troubleshoot Fluid issues in KubeSphere.
What it can touch
- Commands and manifests for: InstallPlan, Dataset, AlluxioRuntime, JuiceFSRuntime, ThinRuntime, DataLoad.
- Resource types via API routes and kubectl: datasets.data.fluid.io, alluxioruntimes.data.fluid.io, juicefsruntimes.data.fluid.io, dataloads.data.fluid.io, thinruntimes.data.fluid.io, allruntimes.
Caveats
- Out of scope: advanced Fluid operations like DataBackup or GooseFS unless requested as follow-up tasks.
- Always use exact user-provided values for name, namespace, mountPoint, replicas, quota, mediumType, and path when generating manifests.
- For uninstall requests, warn about potential removal of CRDs or CR instances.
# KubeSphere Fluid Management Use this skill for the full Fluid lifecycle in KubeSphere: - Install or upgrade the Fluid extension through `InstallPlan` - Query extension status, CRDs, Pods, and logs - Generate `Dataset` manifests with mount configuration - Generate `AlluxioRuntime`, `JuiceFSRuntime`, or `ThinRuntime` manifests for caching - Perform DataLoad for cache warming - Scale runtime replicas - Uninstall the Fluid extension - Troubleshoot Fluid Pods, CRDs, and mount issues Out of scope by default: - Advanced Fluid operations not requested by the user, such as `DataBackup` or `GooseFS` - Deep tiered storage configuration without user requirements If the user explicitly asks for those, acknowledge that they are Fluid capabilities but treat them as a follow-up task. ## Response Rules - Prefer executable output: `InstallPlan` YAML, `Dataset` YAML, `AlluxioRuntime` YAML, kubectl commands, or a short ordered procedure. - Verify the extension name and exact version before generating a final `InstallPlan`. - Default the extension name to `fluid` only if the user context or cluster output does not expose a different resource name. - Use `upgradeStrategy: Manual` unless the user expli
- Response Rules
- CRITICAL: Parameter Handling
- CRITICAL: Operation Scope
- Version Mapping Discovery
- Discovery Commands
- Option 1: Using KubeSphere API (curl)
- CRUD Operations via KubeSphere API
- Option 2: Using kubectl (Direct Cluster Access)
- Option 3: Using ksctl CLI
- When to Use Which Approach
- Example Files
- Install Fluid in KubeSphere
- 1. Pre-check
- 2. InstallPlan Template
kubectl api-resources --api-group data.fluid.io
Discover KubeSphere extension version
kubectl get extensionversions.kubesphere.io -l kubesphere.io/extension-ref=fluid
kubectl get extensionversion fluid-<version> -o yaml
Discover Fluid runtime image or controller version
kubectl get pods -n fluid-system -o wide
kubectl get deploy -n fluid-system alluxio-runtime-controller -o jsonpath='{.spec.template.spec.containers[*].image}'
kubectl describe pod -n fluid-system <fluid-pod>
export KS_HOST="http://<kubesphere-host>" # KubeSphere console URL (required)
export KS_USERNAME="admin" # Username (default: admin)What does the kubesphere-fluid skill do?
KubeSphere Fluid management Skill. Use when user asks to install or enable Fluid, check Fluid status, view Fluid pods/logs/CRDs, create or update Dataset, AlluxioRuntime, JuiceFSRuntime, or ThinRuntime, perform DataLoad or cache warming, scale runtime, or troubleshoot Fluid issues in KubeSphere.
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill kubesphere-fluid --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kubesphere/kubesphere, a repository with 17,016 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.