Skip to content

Commit

Permalink
Kubernetes add DaemonSet more details
Browse files Browse the repository at this point in the history
  • Loading branch information
nvtkaszpir committed Jul 13, 2024
1 parent 7aae43c commit 9b1c90e
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions docs/service.kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 9b1c90e

Please sign in to comment.