From fdb5abb9409131ce209251f43114dd1a27139244 Mon Sep 17 00:00:00 2001 From: tomoya-kawaguchi Date: Thu, 3 Oct 2024 09:00:15 +0900 Subject: [PATCH] docs: removed description of ELB as an example of an not sophisticated Load Balancer Signed-off-by: tomoya-kawaguchi --- docs/content/about/deploying.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/content/about/deploying.md b/docs/content/about/deploying.md index c4ecac34b..402b2f029 100644 --- a/docs/content/about/deploying.md +++ b/docs/content/about/deploying.md @@ -377,9 +377,9 @@ or a token service. If the load balancer has health checks, it is recommended to configure it to consider a 401 response as healthy and any other as down. This secures your registry by ensuring that configuration problems with authentication don't accidentally expose an unprotected registry. If you're -using a less sophisticated load balancer, such as Amazon's Elastic Load -Balancer, that doesn't allow one to change the healthy response code, health -checks can be directed at "/", which always returns a `200 OK` response. +using a less sophisticated load balancer that doesn't allow one to change +the healthy response code, health checks can be directed at "/", which always +returns a `200 OK` response. ## Restricting access