From 76ef9ca9cbba04aa923ba79ca2279b2bd5582702 Mon Sep 17 00:00:00 2001 From: Jim Ma Date: Wed, 29 Sep 2021 11:25:19 +0800 Subject: [PATCH] docs: update kubernetes docs (#696) Signed-off-by: Jim Ma --- docs/en/ecosystem/Kubernetes-with-Dragonfly.md | 6 ++++++ docs/zh-CN/ecosystem/Kubernetes-with-Dragonfly.md | 6 ++++++ 2 files changed, 12 insertions(+) diff --git a/docs/en/ecosystem/Kubernetes-with-Dragonfly.md b/docs/en/ecosystem/Kubernetes-with-Dragonfly.md index e64dbc60d65..bc4ee53ab03 100644 --- 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 index 093b99af6ba..67d1fc2ba87 100644 --- 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: 支持指定仓库**