Zhiqiang ZHOU

Plan: - [ ] Migrate the current validating webhook logic to https://github.com/go-playground/validator, also purge `kubebuilder` annotations - [ ] Provide a `/validate` API Endpoint in chaos-dashboard - [ ] Frontend...

Hi @kkkk4000, we could use `Schedule` and `Workflow` at the same time, but that feature is not supported on dashboard now.. So you could see that you can define `workflow`...

From the man page for tc, tc support bit\bps, kbit\kbps, mbit\mbps as its unit, and the former one means rate in **bits** and the latter one means rate in **bytes**

It seems it's the overhead of the metrics system of Chaos Mesh. We append some annotations on our services like ```yaml annotations: prometheus.io/scrape: "true" prometheus.io/port: "{{ .Values.chaosDaemon.httpPort }}" ``` Maybe...

It's one of the possible explanations, I would try to dive deeper to reproduce and profile.

it looks great! I would take a look later and try it on my machine!

I am not sure about that issue is cause by chaos mesh, or your DNS in Kubernetes Clueter already was broken. Logs from chaos DNS pod might be helpful.

If there are lots of ipbtables rules, it might face some performance issue. And it might also relate to metrics scraped from prometheus. I am not sure which one is...

After the discussion with @g1eny0ung, we find that the validation feature is required to give a better experience to user, for indicating which exact fields are invalid. https://github.com/chaos-mesh/chaos-mesh/issues/2559

> chaos-mesh JVMChaos fault injection does not support JDK8, please see #4184. I would take a look about the JVMChaos compatibility, we could continue discussing in https://github.com/chaos-mesh/chaos-mesh/discussions/4204