Cool. Take into account that daemon set it is created to guarantee having exactly one pod per node. For example, if you had more nodes, more pods for a daemonset will be added. And the same if some crash or you reduce.
If that fits better what you want (sorry I didn't understood before), then don't hesitate to use that. It should be really similar to a deployment (the pod spec is the same, etc.) On Tuesday, December 5, 2017, <mderos...@gmail.com> wrote: > As I said before, using multiple times the command "kubectl apply -f > my-deployment.yaml" (changing from time to time the image version inside > the yaml) I noticed that Kubernetes never deploys 2 pod in a same node. > I tested this behavior many times so yes it's working as I need :) > If I had problems I would use (as an emergency plan) the Daemon Set as you > advised me > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
