From 538dc610d1f9b5885c2938069722ffb65c19714a Mon Sep 17 00:00:00 2001
From: Kirk Larkin <6025110+serpent5@users.noreply.github.com>
Date: Sat, 22 Feb 2020 05:40:47 +0000
Subject: [PATCH] Fix link to nginx + TLS (#19234)

---
 content/en/docs/concepts/services-networking/ingress.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md
index e916e774c4..6739cf1bd0 100644
--- a/content/en/docs/concepts/services-networking/ingress.md
+++ b/content/en/docs/concepts/services-networking/ingress.md
@@ -336,7 +336,7 @@ spec:
 {{< note >}}
 There is a gap between TLS features supported by various Ingress
 controllers. Please refer to documentation on
-[nginx](https://git.k8s.io/ingress-nginx/README.md#https),
+[nginx](https://kubernetes.github.io/ingress-nginx/user-guide/tls/),
 [GCE](https://git.k8s.io/ingress-gce/README.md#frontend-https), or any other
 platform specific Ingress controller to understand how TLS works in your environment.
 {{< /note >}}