docs: update kubernetes docs (#696)

Signed-off-by: Jim Ma <majinjing3@gmail.com>
dragonflyoss · Jun 28, 2023 · 76ef9ca · 76ef9ca
1 parent 513d4f6
commit 76ef9ca
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/docs/en/ecosystem/Kubernetes-with-Dragonfly.md b/docs/en/ecosystem/Kubernetes-with-Dragonfly.md
@@ -17,6 +17,12 @@ When enable runtime configuration in dragonfly, you can skip [Configure Runtime]
 
 #### 1. Docker
 
+> Because the original `daemonset` in Kubernetes did not support `Surging Rolling Update` policy.
+> When kill current dfdaemon pod, the new pod image can not be pulled anymore.
+> Using Docker with dragonfly, when upgrade dfdaemon, should pull newly dfdaemon image manually, or use [ImagePullJob](https://openkruise.io/docs/user-manuals/imagepulljob).
+
+> We did not recommend to using dragonfly with docker in k8s due to many reasons: 1. no fallback image pulling policy. 2. deprecated in Kubernetes.
+
 Dragonfly helm supports config docker automatically.
 
 Config cases:

diff --git a/docs/zh-CN/ecosystem/Kubernetes-with-Dragonfly.md b/docs/zh-CN/ecosystem/Kubernetes-with-Dragonfly.md
@@ -16,6 +16,12 @@
 
 #### 1. Docker
 
+> 因为当前 Kubernetes 里的 `daemonset` 并不支持 `Surging Rolling Update` 策略,
+> 一旦旧的 dfdaemon pod 被删除后，新的 dfdaemon 就再也拉取不了了。
+> 当使用 Docker 时，在升级 dfdaemon 的时候，请先手动拉取新的 dfdaemon 镜像，或者使用 [ImagePullJob](https://openkruise.io/docs/user-manuals/imagepulljob)
+
+> 不推荐在 docker 环境中使用蜻蜓：1. 拉镜像没有 fallback 机制，2. 在未来的 Kubernetes 中已经废弃。
+
 Dragonfly Helm 支持自动更改 docker 配置。
 
 **情况 1: 支持指定仓库**