Re: [kubernetes-users] Run a job on all nodes in the cluster

On Sun, Feb 26, 2017 at 12:53 AM, 'mrpanigale' via Kubernetes user discussion and Q&A wrote: > Hi David, > > I am aware of this already being achievable via Daemonsets, although last > time I checked a Daemonset had to run on all nodes and did not honor a node > selector (this may have been fixed

Re: [kubernetes-users] Run a job on all nodes in the cluster

Hi David, I am aware of this already being achievable via Daemonsets, although last time I checked a Daemonset had to run on all nodes and did not honor a node selector (this may have been fixed). Assuming that this has been fixed, it is often not desirable for a "Puppet" script to run indefini

Re: [kubernetes-users] Run a job on all nodes in the cluster

Just to be clear, DaemonSet does allow all of these > - Run or schedule a job on all machines > - Run or schedule a job on a sub-set of machines using a label selector > - Run or schedule a job on a single machine" It just requires that the "job" be a "run forever" thing, not a "run to completion"

Re: [kubernetes-users] Run a job on all nodes in the cluster

I feel this feature is even more important with the deprecation of Fleet. "For me this is a very important issue but more in the broader scope of Jobs (not just scheduled). CoreOS has deprecated Fleet (distributed systemd). With Fleet one could broadcast a global systemd unit to run on and updat

Re: [kubernetes-users] Run a job on all nodes in the cluster

i opened one yesterday https://github.com/kubernetes/kubernetes/issues/40290 On Monday, January 23, 2017 at 5:26:32 AM UTC-8, David Oppenheimer wrote: > > I would recommend filing a Github issue about this. Discussing on the > mailing list is not good for tracking this long-term. > > > On Mon,

Re: [kubernetes-users] Run a job on all nodes in the cluster

I would recommend filing a Github issue about this. Discussing on the mailing list is not good for tracking this long-term. On Mon, Jan 23, 2017 at 10:30 AM, Ben Kochie wrote: > This sounds like a job that should happen at provisioning time, or by > config management software. > > On Jan 23, 20

Re: [kubernetes-users] Run a job on all nodes in the cluster

This sounds like a job that should happen at provisioning time, or by config management software. On Jan 23, 2017 10:00, "Mayank" wrote: > Yeah, my use case is basically change the permissions of the hostPath so > that my pods running as non root can access it. I dont want a pod running > as dae

Re: [kubernetes-users] Run a job on all nodes in the cluster

Yeah, my use case is basically change the permissions of the hostPath so that my pods running as non root can access it. I dont want a pod running as daemon set for this purpose, since the pod will just be sitting there doing nothing, until a new host appears or a host is reimaged, etc. I belie

Re: [kubernetes-users] Run a job on all nodes in the cluster

I also think having"state changes" it's a bad use case, as it's been pointed out (it can be changed again, etc. No "self healing" once you have state like that, that goes against most of the basic ideas of reconciliation loops in k8s). But I want to add that, although that use case seems like a wr

Re: [kubernetes-users] Run a job on all nodes in the cluster

On Fri, Jan 20, 2017 at 1:40 PM 'Tim Hockin' via Kubernetes user discussion and Q&A wrote: > Concretely the "tweak a sysctl" thing leaves machines that are > "dirty". Once you allow any users to do this, the machines become > less useful for anyone else who doesn't specifically tolerate that > t

Re: [kubernetes-users] Run a job on all nodes in the cluster

If you want to tweak something about a machine, you probably want to actually occasionally check to ensure that it stayed tweaked (no one put it back). So I guess I'd expect the current behavior of daemonset is actually correct for that. On Fri, Jan 20, 2017 at 1:40 PM, 'Tim Hockin' via Kubernetes

Re: [kubernetes-users] Run a job on all nodes in the cluster

Concretely the "tweak a sysctl" thing leaves machines that are "dirty". Once you allow any users to do this, the machines become less useful for anyone else who doesn't specifically tolerate that tweak. Almost every sysctl represents a tradeoff. Optimize for low-latency network? Pay higher CPU

Re: [kubernetes-users] Run a job on all nodes in the cluster

Brandon, would you like to file an issue in kubernetes/kubernetes to start? FWIW the privileged run-to-completion node configuration script is a use case we have also seen at Google, but the semantics get a bit tricky. We could start with just a run-to-completion DaemonSet which I think covers the

Re: [kubernetes-users] Run a job on all nodes in the cluster

I think this would be a nice thing to have. I have seen a few users wanting to do things like run a quick script against all nodes in a cluster that say tweaks a sysctl across the entire fleet. Or, gathers up some setting and pushes the results to some service. I think it would be worthwhile to ga

Re: [kubernetes-users] Run a job on all nodes in the cluster

Unfortunately I don't think it's possible. The documentation for DaemonSet says the RestartPolicy must be Always. If it allowed Never then it would do what you want. On Thu, Jan 19, 2017 at 2:37 PM, Mayank wrote: > Hi All > Is there a way to create a

[kubernetes-users] Run a job on all nodes in the cluster

Hi All Is there a way to create a kubernetes job that runs on all nodes in the cluster and then finishes without creating one job per node using node selector ? Or may be this is enhancement to say run this job on all hosts with regex *.ops.net and viola -Mayank -- You received this message