# Kubesphere Fluid

KubeSphere Fluid management Skill.

- Repository: https://github.com/kubesphere/kubesphere (17074 stars)
- Category: Data and ML
- License: see repository
- Last updated: 2026-07-15
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kubesphere/kubesphere --skill kubesphere-fluid -g -a claude-code -y`
Codex: `npx skills add kubesphere/kubesphere --skill kubesphere-fluid -g -a codex -y`
Cursor: `npx skills add kubesphere/kubesphere --skill kubesphere-fluid -g -a cursor -y`
Gemini CLI: `npx skills add kubesphere/kubesphere --skill kubesphere-fluid -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 explicitly asks for something else.
- Omit optional fields instead of guessing values.
- Before generating Dataset or Runtime, prefer checking the installed API versions:

```bash
kubectl api-resources --api-group data.fluid.io
```

- If the cluster version is unknown and the user only wants an example, use:
  - Dataset: `data.fluid.io/v1alpha1`
  - AlluxioRuntime: `data.fluid.io/v1alpha1`
  - JuiceFSRuntime: `data.fluid.io/v1alpha1`
  - ThinRuntime: `data.fluid.io/v1alpha1`
- For uninstall requests, warn that deleting CRDs or CR instances can remove application configuration.

## CRITICAL: Parameter Handling

**ALWAYS use the exact values provided by the user. Never substitute or guess values.**

When generating YAML manifests:

The rest: https://github.com/kubesphere/kubesphere/blob/HEAD/skills/kubesphere-fluid/SKILL.md