From 529851c30459408f47b869cd185449ca6ae829e5 Mon Sep 17 00:00:00 2001
From: Godswill012 <142279804+Godswill012@users.noreply.github.com>
Date: Mon, 29 Sep 2025 12:25:09 -0500
Subject: [PATCH] Update Advanced_Interview_Questions.md

---
 Advanced_Interview_Questions.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Advanced_Interview_Questions.md b/Advanced_Interview_Questions.md
index 38f5327..3748b3d 100644
--- a/Advanced_Interview_Questions.md
+++ b/Advanced_Interview_Questions.md
@@ -2,3 +2,5 @@
 
 Having multiple master nodes ensures that services remain available should master node(s) fail. In order to facilitate availability of master services, they should be deployed with odd numbers (e.g. 3,5,7,9 etc.) so quorum (master node majority) can be maintained should one or more masters fail. In the HA scenario, Kubernetes will maintain a copy of the etcd databases on each master, but hold elections for the control plane function leaders kube-controller-manager and kube-scheduler to avoid conflicts. The worker nodes can communicate with any master’s API server through a load balancer.
 Deploying with multiple masters is the minimum recommended configuration for most production clusters.
+
+