Failed to update records: Post https://chaos-mesh-controller-manager.chaos-mesh.svc:443/mutate-chaos-mesh-org-v1alpha1-networkchaos?timeout=5s: context deadline exceeded about chaos-mesh HOT 7 CLOSED

I think maybe the http body is too big and the client timeout is too short.

So should we record all events in containerRecords?

from chaos-mesh.

The solution for successful deletion was found.

Update timeoutSeconds in kind MutatingWebhookConfiguration.

from chaos-mesh.

I'm also having this problem, trying to update the timeoutSeconds now to see if that fixes it.

from chaos-mesh.

I think my actual problem is frequent restarts, because applying the update to timeoutSeconds didn't work, because the container keeps getting re-created: #4351

from chaos-mesh.

The solution for successful deletion was found.

Update timeoutSeconds in kind MutatingWebhookConfiguration.

@happy-v587 Got it! If this update solves your problem, would you mind helping us open a PR for this section in helm templates?

from chaos-mesh.

I found that this parameter already exists, how can I modify it.

https://github.com/chaos-mesh/chaos-mesh/blob/release-2.7/helm/chaos-mesh/values.yaml#L539

from chaos-mesh.

I found that this parameter already exists, how can I modify it.

release-2.7/helm/chaos-mesh/values.yaml#L539

@happy-v587 😮 Oh...if this parameter has already existed, then no additional changes are required. People can use it to increase the timeout. Thanks for the correction!

from chaos-mesh.