From ffec0d42c39524b1f375800f2a30a534b41e18da Mon Sep 17 00:00:00 2001
From: k8s-ci-robot <k8s-ci-robot@users.noreply.github.com>
Date: Tue, 5 Jan 2021 14:28:55 +0000
Subject: [PATCH] Deploy GitHub Pages

---
 sitemap.xml.gz                                  | Bin 686 -> 686 bytes
 .../nginx-configuration/annotations/index.html  |   2 +-
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index 0b3a90f810ad30ff10f913e391b51ef05f62a89f..40cf5217045714be78a6f0a8ca32dd9012d94f78 100644
GIT binary patch
delta 15
WcmZ3-x{j4izMF$%S@}k`6-)pm%LJtW

delta 15
WcmZ3-x{j4izMF$1qI4tM3MK#|?F3Z-

diff --git a/user-guide/nginx-configuration/annotations/index.html b/user-guide/nginx-configuration/annotations/index.html
index c84767a33..aca7254f4 100644
--- a/user-guide/nginx-configuration/annotations/index.html
+++ b/user-guide/nginx-configuration/annotations/index.html
@@ -2726,7 +2726,7 @@ it is impossible to configure a proper rate limit using stock NGINX functionalit
 Global Rate Limiting overcome this by using <a href="https://github.com/ElvinEfendi/lua-resty-global-throttle">lua-resty-global-throttle</a>. <code>lua-resty-global-throttle</code> shares its counters via a central store such as <code>memcached</code>.
 The obvious shortcoming of this is users have to deploy and operate a <code>memcached</code> instance
 in order to benefit from this functionality. Configure the <code>memcached</code>
-using <a href="../configmap/#memcached">these configmap settings</a>.</p>
+using <a href="../configmap/#global-rate-limit">these configmap settings</a>.</p>
 <p><strong>Here are a few remarks for ingress-nginx integration of <code>lua-resty-global-throttle</code>:</strong></p>
 <ol>
 <li>We minimize <code>memcached</code> access by caching exceeding limit decisions. The expiry of