You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Why use a DaemonSet?
Is there a way to avoid the scenario above? i.e. run the pod once and only once
Thanks in advance
The text was updated successfully, but these errors were encountered:
@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.
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:
Thanks in advance
The text was updated successfully, but these errors were encountered: