From 9b1c90e42f6bc25042d36184322c38544e375aac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Socho=C5=84?= Date: Sat, 13 Jul 2024 22:52:27 +0200 Subject: [PATCH] Kubernetes add DaemonSet more details --- docs/service.kubernetes.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/service.kubernetes.md b/docs/service.kubernetes.md index 5985723..3bf608f 100644 --- a/docs/service.kubernetes.md +++ b/docs/service.kubernetes.md @@ -40,6 +40,11 @@ for the content you can use with a [kustomize](https://kustomize.io/). The difference between the DaemonSet and Deployment is that with the Deployment kubernetes will try to spawn new pods even if node is not available. DaemonSet it is better when you have to use directly attached devices to the hosts. + Of course in that case you will need a daemonset per camera per host, + and separate config for each camera/host, and you would need the same with + a deployment, but at least when node is gone you are not getting non-schedulable + pod every few minutes. With a daemonset when node is gone, then pod is gone + and k8s is not trying to spawn new pods. ## More copies