From 743fbb1da4ae6e35f70bf14d6feb0b0aadf48cd9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lucas=20Serv=C3=A9n=20Mar=C3=ADn?= Date: Wed, 12 May 2021 14:35:16 +0200 Subject: [PATCH] docs/peer-validation: fix code-block MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Lucas Servén Marín --- docs/peer-validation.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/peer-validation.md b/docs/peer-validation.md index 09ae036..f521eea 100644 --- a/docs/peer-validation.md +++ b/docs/peer-validation.md @@ -25,6 +25,7 @@ One way to do this is to use the [kube-webhook-certgen](https://github.com/jet/k The following snippet can be used to run kube-webhook-certgen in a Docker container to create a Secret and certificate signing request: ```shell docker run -v /path/to/kubeconfig:/kubeconfig.yaml:ro jettech/kube-webhook-certgen:v1.5.2 --kubeconfig /kubeconfig.yaml create --namespace kilo --secret-name peer-validation-webhook-tls --host peer-validation,peer-validation.kilo.svc --key-name tls.key --cert-name tls.config +``` Now, the Kubernetes API server can be told what CA to trust by patching the ValidatingWebhookConfiguration with the newly created CA bundle: ```shell