From e0f6925aeed9dd302b3b5ab33dabcf9b06b5f02d Mon Sep 17 00:00:00 2001 From: Knative Prow Robot Date: Fri, 26 Jan 2024 09:22:42 +0000 Subject: [PATCH] Update transport-encryption.md (#5832) Fix: https://github.com/knative/docs/issues/5823 In the doc linked below, https://knative.dev/docs/eventing/experimental-features/transport-encryption/#prerequisites Eventing installation should be linked to https://knative.dev/docs/install/ Co-authored-by: Yan Song Liu --- docs/eventing/experimental-features/transport-encryption.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/eventing/experimental-features/transport-encryption.md b/docs/eventing/experimental-features/transport-encryption.md index eb4afcb8a63..9f15a9014ef 100644 --- a/docs/eventing/experimental-features/transport-encryption.md +++ b/docs/eventing/experimental-features/transport-encryption.md @@ -24,7 +24,7 @@ Event producers are be able to connect to HTTPS endpoints with cluster-internal - In order to enable the transport encryption feature, you will need to install cert-manager operator by following [the cert-manager operator installation instructions](https://cert-manager.io/docs/installation/). -- [Eventing installation](./../../install) +- [Eventing installation](./../../../install) ## Installation @@ -386,4 +386,4 @@ Example output: < date: Thu, 03 Aug 2023 10:08:22 GMT < * Connection #0 to host broker-ingress.knative-eventing.svc.cluster.local left intact -``` \ No newline at end of file +```