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

Memory stressor is not accepting time field #4424

Open
pe55a opened this issue May 23, 2024 · 2 comments
Open

Memory stressor is not accepting time field #4424

pe55a opened this issue May 23, 2024 · 2 comments

Comments

@pe55a
Copy link

pe55a commented May 23, 2024

Bug Report

What version of Chaos Mesh are you using?
2.6.3

What did you do? / Minimal Reproducible Example
According to the documentation, the memory stressor should accept time as arguments. I created a YAML file where I have the time field and tried to apply it to k8s.

What did you expect to see?
experiment should have been created successfully

What did you see instead?
StressChaos in version "v1alpha1" cannot be handled as a StressChaos: strict decoding error: unknown field "spec.stressors.memory.time"

@STRRL
Copy link
Member

STRRL commented May 28, 2024

Hi @pe55a, that's an issue on the documentation, we should use spec.duration to setup how long the chaos experiment effect.

Could you help us to address the problem on documentation by deleting this field?

Thanks.

@pe55a
Copy link
Author

pe55a commented May 29, 2024

I'm not sure that time field is supposed to setup how long the chaos experiment execute.

from the doc:
time: Specifies the time to reach the memory size. The growth model is a linear model.

So, if I understand this right, time is the time that one can define in order for the chaos to reach the mem size and then keep it at that level till the end of the experiment. This could be useful for testing autoscaling processes when memory increases suddenly or linearly

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