Zhiqiang ZHOU

maybe you should take a try with `target` https://chaos-mesh.org/docs/simulate-network-chaos-on-kubernetes/#field-description  the network chaos experiment you provided would blackhole each "foo" pod, and also block the connections between "foo" pods.

hI @BasiurII , that's great to sound that you already resolved the issue. > I find that Previously injected network delay anomalies are logged whereas stress tests are not. What...

what's the "Kind" of the resources you listed?

I am not pretty sure what you want to do. If you want to cleanup your environment and remove chaos mesh with chaos experiments, please follow the documentation: https://chaos-mesh.org/docs/uninstallation/#uninstall-chaos-mesh-manually If...

for cleanup / manually uninstall chaos mesh, you could follow this doc: https://chaos-mesh.org/docs/uninstallation/#uninstall-chaos-mesh-manually

for your specific situation, you should remove the webhook first, then remove rest stuff

It seems there have been a long time since the last update, I think I could take over this PR and push it get merged. I would take a look...

I found setting up a local dev env with OIDC would be very tricky, so I also write a doc for it: https://github.com/chaos-mesh/website/pull/418

basically it could works now, but I am considering how to make it clean

Hi @g1eny0ung , I noticed we're using a `` here for the OIDC Login button. https://github.com/chaos-mesh/chaos-mesh/blob/23f80553b7bdb69da179002c1effe3178ebfd03e/ui/app/src/components/TopContainer/Auth.tsx#L84-L95 Could we replace it with OIDC icon like this: https://fontawesome.com/v5/icons/openid?f=brands&s=solid? I noticed that icons...