Replies: 6 comments
-
Here are my suggestions for changes to the dashboard UI: |
Beta Was this translation helpful? Give feedback.
-
Hi, what about adding a Kubernetes experiment which triggers to Kubernetes node to crash/failure/restart/stop?
As a user of chaos engineering, I want to operate on a node level and create a hypothesis such as "What happens to my application when one of my Kubernetes nodes crashed/failure/restart?", What happens to my application if there is no enough memory or CPU worker node left on worker node? It would be good to see the results of such experiments I think.
I am not familiar with you codebase but first we should decide if this idea make a sense. If so we could proceed with the design... |
Beta Was this translation helpful? Give feedback.
-
Generally, would be good to consider the use case of using the console primarily to design experiments that will be exported and run in other ways (e.g. in pipelines).
|
Beta Was this translation helpful? Give feedback.
-
Another idea for the UI is the some way to hide buttons that are not relevant. For example at least two if not three of aws/azure/gcp are irrelevant for every cluster and could be hidden. And in a shared cluster, a namespace user probably should only have access to experiments that are limited to the namespace. Maybe only show buttons for which the authenticated user/token has privileges to the underlying CRD? |
Beta Was this translation helpful? Give feedback.
-
s there a plan to support HTTPS fault injection |
Beta Was this translation helpful? Give feedback.
-
Currently an experiment created runs only once and to rerun we need to recreated the experiment or upload the yaml file again. This keeps on accumulating the experiments till we archive it. It would be nice to have feature where we can create /configure an experiment and rerun the same whenever required. This would save a lot of time and effort. |
Beta Was this translation helpful? Give feedback.
-
Hello everyone!
As the maintainer of our open-source project, I am excited to announce the next release is version 2.7. To make this release the best it can be and serve our community's needs, I'm reaching out to ask for your help in collecting new features.
If you have any ideas or suggestions for features that you would like to see in the upcoming release, please share them in this thread. We want to hear from you and ensure that the new release addresses the needs of our users and contributors as much as possible.
Here are some guidelines to follow while sharing your suggestions:
Please contribute your ideas so that we can make version 2.7 a great success! Thank you in advance for your help and support.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions