update docs on leader election (projectcontour#4943)

Signed-off-by: Steve Kriss <[email protected]> Co-authored-by: Bhagwat kumar Singh <[email protected]>
sunjayBhatia · Dec 20, 2022 · d4591c0 · d4591c0
1 parent 960e620
commit d4591c0
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 2 deletions.
diff --git a/site/content/docs/main/architecture.md b/site/content/docs/main/architecture.md
@@ -47,9 +47,13 @@ The following API objects are watched:
 ### Contour Deployment
 
 Contour is deployed in the cluster using a Kubernetes Deployment.
-It has built-in leader election so the total number of replicas does not matter.
+It has built-in leader election which is responsible for updating httproxy/ingress/gateway api resources via Kube API server.
 All instances are able to serve xDS configuration to any Envoy instance, but only the leader can write status back to the API server.
 
+The data being served from contour instances are eventually consistent in an HA based deployment.
+However HA mode is operationally scalable when you have high request rate from envoy to contour as requests are loadbalanced among contour instances.
+This also helps availability zone /data center degradation events as your service continue to function.
+
 ### Envoy Deployment
 
 Envoy can be deployed in two different models, as a Kubernetes Daemonset or as a Kubernetes Deployment. 

diff --git a/site/content/docs/v1.23.2/architecture.md b/site/content/docs/v1.23.2/architecture.md
@@ -47,9 +47,13 @@ The following API objects are watched:
 ### Contour Deployment
 
 Contour is deployed in the cluster using a Kubernetes Deployment.
-It has built-in leader election so the total number of replicas does not matter.
+It has built-in leader election which is responsible for updating httproxy/ingress/gateway api resources via Kube API server.
 All instances are able to serve xDS configuration to any Envoy instance, but only the leader can write status back to the API server.
 
+The data being served from contour instances are eventually consistent in an HA based deployment.
+However HA mode is operationally scalable when you have high request rate from envoy to contour as requests are loadbalanced among contour instances.
+This also helps availability zone /data center degradation events as your service continue to function.
+
 ### Envoy Deployment
 
 Envoy can be deployed in two different models, as a Kubernetes Daemonset or as a Kubernetes Deployment.