Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why use a DaemonSet in Kubernetes? #150

Closed
mzeljkovic opened this issue Feb 17, 2020 · 2 comments
Closed

Why use a DaemonSet in Kubernetes? #150

mzeljkovic opened this issue Feb 17, 2020 · 2 comments

Comments

@mzeljkovic
Copy link

Hi There,

Just curious why use a DaemonSet in Kubernetes. DaemonSet restarts the pumba pods once they complete. If you have a requirement to run a single/once off chaos test e.g. add 300ms delay for 5mins to container x, this means that after 5mins the pod will complete and will then be restarted by the DaemonSet, making it impossible to run a single/once off test.

So I guess there are 2 questions here:

  1. Why use a DaemonSet?
  2. Is there a way to avoid the scenario above? i.e. run the pod once and only once

Thanks in advance

@alexei-led
Copy link
Owner

@mzeljkovic there is a point in what you say. I'm thinking to make it a more K8s-friendly.
Currently, DaemonSet deployment does not suit your use case. Probably, you could use K8s Job with nodeSelector running it on specified nodes.

@mzeljkovic
Copy link
Author

Thanks a million for the quick response @alexei-led

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants