From 130c6957ebc8122e6cd05bd45bed54ad039a4b1b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Patryk=20Ma=C5=82ek?= Date: Thu, 12 Dec 2024 19:24:49 +0100 Subject: [PATCH] Update app/_src/kubernetes-ingress-controller/guides/security/verify-upstream-tls.md --- .../guides/security/verify-upstream-tls.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/app/_src/kubernetes-ingress-controller/guides/security/verify-upstream-tls.md b/app/_src/kubernetes-ingress-controller/guides/security/verify-upstream-tls.md index 4cf1d8402f33..a6f5d06a7322 100644 --- a/app/_src/kubernetes-ingress-controller/guides/security/verify-upstream-tls.md +++ b/app/_src/kubernetes-ingress-controller/guides/security/verify-upstream-tls.md @@ -16,9 +16,11 @@ shows how to make this happen using the `BackendTLSPolicy` (when using Gateway A ## Set up an upstream service with TLS Before we configure {{ site.kic_product_name }} to verify the certificate of the upstream service, we need to set up an -upstream service that handles TLS. We can use the `kong/goecho` service as an example. It is a simple echo server that +upstream service that handles TLS. We can use the [`kong/goecho`][kong_goecho] service as an example. It is a simple echo server that can be configured to serve HTTPS on an arbitrary port using a TLS certificate and key pair. +[kong_goecho]: https://github.com/kong/go-echo + ### Create a certificate chain To showcase all the possible configurations, we will create a certificate chain with a root CA, an intermediate CA, and