Zhiqiang ZHOU

currenly the payload of StressChaos would NOT executed in the same pid namespace of the pod, so most of monitoring tools would not should it properly. and there is not...

Hi @vaniog , thank you sooo much about your contribution! ❤️ However, this huge PR is not covered by any maintainer's domain experiences, which means, we have no related experiences...

@Hamtaro-i could you provide more info like container images, linux distro and version, java runtime kind / versions ? JVMChaos need to make java-agent to connect to the java runtime....

it might be. No, we do not have this detailed docs.

Hi @grzesuav , I am afraid not. even recover needs some reconciliation process inside the controller, which means `status` need to be updated, and obviously it cannot be done now....

Could you tell us how many pods were affected approximately in this Network Chaos? I think we can try to reproduce it and fix it. This part needs some improvement....

> To be honest in that case some trimming would be enough. Actually I want to delete this resource but it stuck in deletion maybe could use PATCH or other...

> > [chaos-mesh/helm/chaos-mesh/values.yaml](https://github.com/chaos-mesh/chaos-mesh/blob/43653eb24147a02ac833833259780416e2811891/helm/chaos-mesh/values.yaml#L145) > > Line 145 in [43653eb](/chaos-mesh/chaos-mesh/commit/43653eb24147a02ac833833259780416e2811891) > > chaosdSecurityMode: true > > 涉及的配置在这里，默认是出于安全考虑，测试的话可以禁用掉。 > > 赞，设置了这个后没报必须https了，但变成了Failed to apply chaos： Post “[http://192.168.7.3/api/attack/stress”](http://192.168.7.3/api/attack/stress%E2%80%9D) dial tcp 192.168.7.3:80: connect:connection refused 又是哪个配置指定了80端口吗，可以修改吗...

Hi @kbabiak, thanks for your contribution! I am not sure about we'd merge this PR into codebase, it seems rather than hide this option on frontend, it's better to use...

@copilot is there a way to unify this config for both controller side and dashboard side?