Add a solution to InternalError webhook context timedout

[justmike1]

Context

#1527

[toast-gear]

Add the entry to the pages index

[mumoshu]

Hey! Thanks for your contribution.
To be clear, this isn't always correct.
context deadline exceeded on mutation and validation can happen for two reasons:

• Your K8s control-plane is somehow unable to access the K8s service's clusterIP associated with the admission webhook server (of ARC)
  • Possible causes: (1)You're running apiserver as a binary and you didn't make service cluster IPs available to the host network or (2)You're running the apiserver in the pod but your pod network (i.e. CNI plugin installation and config) is not good so your pods(like kube-apiserver) in the K8s control-plane nodes can't access ARC's admission webhook server pod(s) in probably data-plane nodes
• Your cluster has dangling "admissionwebhookconfiguration" and "validatingwebhookconfiguration" from probably previous installation of ARC
  • In that case, isolate the dangling resources by running kubectl get {mutating,validating}webhookconfiguration and only after that, delete only outdated ones like this solution

That said, I'm unsure how I can reorganize my full explanation to a more approachable guide. So... I'd greatly appreciate it if you could somehow enhance this guide to reflect the above 🙏 Thanks!

[mikejoseph-ef]

Np!

Edit: done.
It is hard to sort it out but I did it in a way that would be considered fine if I was going through it for the first time or such... hopefully that suits what you wanted...

[mumoshu]

LGTM. Thanks a lot for your contribution!