From fbfd5d05b5377baadc57d1724df4530dad5dfafc Mon Sep 17 00:00:00 2001 From: akp1410 Date: Thu, 29 Jan 2026 11:59:46 +0530 Subject: [PATCH 1/2] Updated Text Content --- Advanced_Interview_Questions.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Advanced_Interview_Questions.md b/Advanced_Interview_Questions.md index 38f5327..98b8e23 100644 --- a/Advanced_Interview_Questions.md +++ b/Advanced_Interview_Questions.md @@ -2,3 +2,4 @@ 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. +######################################################################################################## From 06dade515f3d471ec1470fe83002e73e11ae09ef Mon Sep 17 00:00:00 2001 From: akp1410 Date: Thu, 29 Jan 2026 15:14:39 +0530 Subject: [PATCH 2/2] Add multiplication script --- multiply.sh | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 multiply.sh diff --git a/multiply.sh b/multiply.sh new file mode 100644 index 0000000..12b3937 --- /dev/null +++ b/multiply.sh @@ -0,0 +1,3 @@ +#!/bin/bash + +echo "Multiplication"