Docs: combined webhook troubleshooting docs and prune docs versions (a…

…ws#3231)

website/config.yaml

@@ -70,6 +70,7 @@ params:
   versions:
     - v0.22.1
     - v0.21.1
+    - v0.20.0
     - preview
 menu:
   main:

website/content/en/preview/troubleshooting.md

@@ -8,18 +8,6 @@ description: >
 
 ## Installation
 
-### Installation Webhook Timeout on v0.19.0+
-
-If you're upgrading from before `v0.19.0` to `v0.19.0+`, are using ArgoCD, and are unable to call your webhook with the following error, your ArgoCD sync may be trying to check for webhooks that no longer exist, since the name has changed.
-
-`Internal error occurred: failed calling webhook "validation.webhook.provisioners.karpenter.sh":`
-
-Delete the stale webhooks. After the following, sync ArgoCD once again.
-```
-kubectl delete mutatingwebhookconfigurations defaulting.webhook.provisioners.karpenter.sh
-kubectl delete validatingwebhookconfiguration validation.webhook.provisioners.karpenter.sh
-```
-
 ### Missing Service Linked Role
 Unless your AWS account has already onboarded to EC2 Spot, you will need to create the service linked role to avoid `ServiceLinkedRoleCreationNotPermitted`.
 ```
@@ -104,9 +92,22 @@ kubectl get nodes -ojsonpath='{range .items[*].metadata}{@.name}:{@.finalizers}{
 
 ## Webhooks
 
-### Failed calling webhook "defaulting.webhook.provisioners.karpenter.sh"
+### Failed calling webhook "validation.webhook.provisioners.karpenter.sh"
+
+If you are not able to create a provisioner due to `Internal error occurred: failed calling webhook "validation.webhook.provisioners.karpenter.sh":`
+
+Webhooks were renamed in v0.19.0. There's a bug in ArgoCD's upgrade workflow where webhooks are leaked. This results in Provisioner's failing to be validated, since the validation server no longer corresponds to the webhook definition.
+
+Delete the stale webhooks.
+```
+kubectl delete mutatingwebhookconfigurations defaulting.webhook.provisioners.karpenter.sh
+kubectl delete validatingwebhookconfiguration validation.webhook.provisioners.karpenter.sh
+```
+
+### Failed calling webhook "defaulting.webhook.karpenter.sh"
+
+If you are not able to create a provisioner due to `Error from server (InternalError): error when creating "provisioner.yaml": Internal error occurred: failed calling webhook "defaulting.webhook.karpenter.sh": Post "https://karpenter-webhook.karpenter.svc:443/default-resource?timeout=10s": context deadline exceeded`
 
-If you are not able to create a provisioner due to `Error from server (InternalError): error when creating "provisioner.yaml": Internal error occurred: failed calling webhook "defaulting.webhook.provisioners.karpenter.sh": Post "https://karpenter-webhook.karpenter.svc:443/default-resource?timeout=10s": context deadline exceeded`
 
 Verify that the karpenter pod is running (should see 2/2 containers with a "Ready" status)
 ```text