From f3f56abd0ce817ab31cc1cc820787c6552ec5511 Mon Sep 17 00:00:00 2001
From: Nikhil K <84435819+knikhil42@users.noreply.github.com>
Date: Wed, 3 Jan 2024 21:50:42 +0530
Subject: [PATCH] Update README.md

---
 README.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 761a6ab..a7e56ce 100644
--- a/README.md
+++ b/README.md
@@ -4,15 +4,17 @@
 
 There are three main pre-requisites for a production grade cdefense installation on-premises
 
-1. A managed Postgres instance (for AWS RDS db.r5.large)
+1. A managed Postgres instance (for ex. AWS RDS db.r5.large)
     1. enable automated backups
-2. A kubernetes cluster (/examples/eks) with at least two nodegroups
+2. A Kubernetes cluster (EKS/GKE/AKS) (/examples/eks) with at least two nodegroups
     1. node group for jobs
         1. each node has { label: job }
     2. node group for all else
         1. (optional) each node has { label: cdefense }
 3. A cluster auto-scaler
 
+Note: `kubectl get nodes`
+
 ## WARNINGS
 
 - Database URI has to be the Internal URI valid inside the private network