Update webhook documentation and manifests (#3645)

* Update webhook documentation and manifests * Update docs/operating-eck/webhook.asciidoc Co-authored-by: Peter Brachwitz <[email protected]> * Fix webhook-name description Co-authored-by: Peter Brachwitz <[email protected]>
elastic · Aug 26, 2020 · 090d2aa · 090d2aa
1 parent d24e527
commit 090d2aa
Show file tree

Hide file tree

Showing 6 changed files with 194 additions and 123 deletions.
diff --git a/docs/eck-attributes.asciidoc b/docs/eck-attributes.asciidoc
@@ -2,3 +2,4 @@
 :eck_crd_version: v1
 :eck_release_branch: 1.2
 :eck_github: https://github.com/elastic/cloud-on-k8s
+:eck_resources_list: Elasticsearch, Kibana, APM Server, Enterprise Search, and Beats
diff --git a/docs/operating-eck/operator-config.asciidoc b/docs/operating-eck/operator-config.asciidoc
@@ -31,7 +31,6 @@ ECK can be configured using either command line flags or environment variables.
 |operator-namespace |"" |Namespace the operator runs in. Required.
 |webhook-cert-dir |"{TempDir}/k8s-webhook-server/serving-certs" |Path to the directory that contains the webhook server key and certificate.
 |webhook-name |"elastic-webhook.k8s.elastic.co" |Name of the Kubernetes ValidatingWebhookConfiguration resource. Only used when `enable-webhook` is true.
-|webhook-pods-label |"" |Label used to select pods running the webhook server.
 |webhook-secret |"" | K8s secret mounted into the path designated by webhook-cert-dir to be used for webhook certificates.
 |===
 

diff --git a/docs/operating-eck/troubleshooting/common-problems.asciidoc b/docs/operating-eck/troubleshooting/common-problems.asciidoc
@@ -30,7 +30,7 @@ Error from server (Timeout): error when creating "elasticsearch.yaml": Timeout:
 ....
 
 
-This error is usually an indication of a problem communicating with the validating webhook. If you are running ECK on a private Google Kubernetes Engine (GKE) cluster, you may need to link:https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules[add a firewall rule] allowing port 9443 from the API server. Another possible cause for failure is if a strict <<{p}-webhook-network-policies,network policy>> is in effect. Refer to the <<{p}-webhook-troubleshooting,webhook troubleshooting>> documentation for  more details and workarounds.
+This error is usually an indication of a problem communicating with the validating webhook. If you are running ECK on a private Google Kubernetes Engine (GKE) cluster, you may need to link:https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules[add a firewall rule] allowing port 9443 from the API server. Another possible cause for failure is if a strict network policy is in effect. Refer to the <<{p}-webhook-troubleshooting-timeouts,webhook troubleshooting>> documentation for  more details and workarounds.
 
 [id="{p}-{page_id}-owner-refs"]
 == Copying secrets with Owner References