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
We would like to run kurtosis managed stack for long-ish durations (like a week) for stress-testing, memory leaks detection, chaos-engineering, and so forth.
For this, it would be great if we can configure the type of the workload that kurtosis would create (i.e. Pod, Deployment, StatefulSet, DaemonSet).
Desired behaviour
Currently kurtosis only uses Pod resources for the workloads. These do not survive host migrations, and would not be recreated if killed externally.
Also, for the storage in k8s kurtosis uses PVCs. It would make more sense to use StatefulSets in those situations.
How important is this to you?
Painful; the lack of this feature makes using Kurtosis frictionful.
What area of the product does this pertain to?
CLI: the Command Line Interface
The text was updated successfully, but these errors were encountered:
Background & motivation
We would like to run
kurtosis
managed stack for long-ish durations (like a week) for stress-testing, memory leaks detection, chaos-engineering, and so forth.For this, it would be great if we can configure the type of the workload that kurtosis would create (i.e.
Pod
,Deployment
,StatefulSet
,DaemonSet
).Desired behaviour
Currently
kurtosis
only usesPod
resources for the workloads. These do not survive host migrations, and would not be recreated if killed externally.Also, for the storage in k8s
kurtosis
uses PVCs. It would make more sense to useStatefulSet
s in those situations.How important is this to you?
Painful; the lack of this feature makes using Kurtosis frictionful.
What area of the product does this pertain to?
CLI: the Command Line Interface
The text was updated successfully, but these errors were encountered: