fluid-cloudnative · btxu-db · Aug 16, 2026 · Aug 27, 2026
diff --git a/docs/en/TOC.md b/docs/en/TOC.md
@@ -23,6 +23,7 @@
     - [Data Preloading](samples/data_warmup.md)
     - [CacheRuntime Data Operations](samples/cacheruntime/cacheruntime_data_operations.md)
     - [Use Curvine as CacheRuntime for Data Caching](samples/cacheruntime/curvine_cache_runtime.md)
+    - [Deploy Mooncake with CacheRuntime](samples/cacheruntime/mooncake_cache_runtime.md)
     - [Cache Runtime Manually Scaling](samples/dataset_scaling.md)
     - [Automatic Cleanup Data Operation](samples/automatic_clean_up_data_operation.md)
   + Security

diff --git a/docs/en/dev/generic_cache_runtime_integration.md b/docs/en/dev/generic_cache_runtime_integration.md
@@ -176,6 +176,17 @@ topology:
           imagePullPolicy: IfNotPresent
 ```
 
+#### Cache Systems Without a Client Component
+
+The master, worker and client components under `topology` are all optional in the API. You may omit the **client** component if the underlying cache system has both of the following characteristics:
+
+1. **No POSIX mount semantics**: the cache system itself provides no FUSE-like mount capability.
+2. **Applications connect directly**: applications read and write against the master/worker through the cache system's own SDK or RPC client, without relying on a mount point.
+
+In that case the Master and Worker components start as usual, the Dataset reaches the Bound phase as usual, and cache status is still reported through the ReportSummary script.
+
+Note that Fluid still creates a PVC/PV for such a Dataset and reports them as Bound, but an application pod that mounts the PVC stays in ContainerCreating forever (reporting `timeout waiting for FUSE mount point`). For this kind of cache system, applications should talk to the cache service directly instead of going through the Dataset → PVC → volumeMounts path. For a complete configuration example, see [Deploy Mooncake with CacheRuntime](../samples/cacheruntime/mooncake_cache_runtime.md).
+
 ### Step 2.5 User Creates Runtime
 
 ```yaml

diff --git a/docs/en/samples/cacheruntime/mooncake_cache_runtime.md b/docs/en/samples/cacheruntime/mooncake_cache_runtime.md
diff --git a/docs/zh/TOC.md b/docs/zh/TOC.md
@@ -28,6 +28,7 @@
     - [数据预加载](samples/data_warmup.md)
     - [CacheRuntime 数据操作](samples/cacheruntime/cacheruntime_data_operations.md)
     - [使用 Curvine 作为 CacheRuntime 进行数据缓存](samples/cacheruntime/curvine_cache_runtime.md)
+    - [使用 CacheRuntime 部署 Mooncake](samples/cacheruntime/mooncake_cache_runtime.md)
     - [Cache Runtime手动扩缩容](samples/dataset_scaling.md)
     - [数据操作自动清理](samples/automatic_clean_up_data_operation.md)
   + 安全

diff --git a/docs/zh/dev/generic_cache_runtime_integration.md b/docs/zh/dev/generic_cache_runtime_integration.md
@@ -175,6 +175,17 @@ topology:
           - custom-endpoint.sh
           imagePullPolicy: IfNotPresent
 ```
+#### 无 Client 组件的场景
+
+topology 中的 master、worker、client 三个组件在 API 上均为可选。如果底层缓存系统具备以下特征，可以**不声明 client**：
+
+1. **无 POSIX 挂载语义**：缓存系统本身不提供 FUSE 之类的挂载能力
+2. **应用直连访问**：应用通过缓存系统自带的 SDK 或 RPC 客户端直接读写 master/worker，不依赖挂载点
+
+此时 Master 与 Worker 组件正常拉起，Dataset 正常进入 Bound 状态，缓存状态也会通过 ReportSummary 脚本正常上报。
+
+需要注意的是，Fluid 仍会为该 Dataset 创建 PVC/PV 且状态为 Bound，但业务 Pod 挂载该 PVC 会一直停留在 ContainerCreating（报 timeout waiting for FUSE mount point）。这类缓存系统应由应用直连缓存服务读写，不要走 Dataset → PVC → volumeMounts 这条路径。完整配置示例参见 [使用 CacheRuntime 部署 Mooncake](../samples/cacheruntime/mooncake_cache_runtime.md)。
+
 
 ### 步骤2.5 用户创建Runtime