PoC / Test / Minimum Deployment
This topology is designed for Proof of Concept (PoC), test, and minimum deployment scenarios.Server 1
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 8 Core
RAM: 16 GB
Disk: 200 GB
Installations: Kubernetes Control-Plane, Elasticsearch (Master+Data), Replica set MongoDB Single Instance
CPU: 8 Core
RAM: 16 GB
Disk: 200 GB
Installations: Kubernetes Control-Plane, Elasticsearch (Master+Data), Replica set MongoDB Single Instance
Server 2
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 8 Core
RAM: 12 GB
Disk: 80 GB
Installations: Kubernetes Worker
CPU: 8 Core
RAM: 12 GB
Disk: 80 GB
Installations: Kubernetes Worker
Professional Deployment
This topology is designed for professional production environments.Server 1
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 8 Core
RAM: 32 GB
Disk: 1 TB
Installations: Kubernetes Control-Plane, Elasticsearch (Master+Data), Replica set MongoDB Single Instance
CPU: 8 Core
RAM: 32 GB
Disk: 1 TB
Installations: Kubernetes Control-Plane, Elasticsearch (Master+Data), Replica set MongoDB Single Instance
Server 2
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 10 Core
RAM: 12 GB
Disk: 80 GB
Installations: Kubernetes Worker
CPU: 10 Core
RAM: 12 GB
Disk: 80 GB
Installations: Kubernetes Worker
Server 3
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 10 Core
RAM: 12 GB
Disk: 80 GB
Installations: Kubernetes Worker
CPU: 10 Core
RAM: 12 GB
Disk: 80 GB
Installations: Kubernetes Worker
High Available Deployment
This topology is designed for production environments with high availability requirements.Kubernetes Control-Plane Nodes
Server 1
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 4 Core
RAM: 4 GB
Disk: 80 GB
Installations: Kubernetes Control-Plane
CPU: 4 Core
RAM: 4 GB
Disk: 80 GB
Installations: Kubernetes Control-Plane
Server 2
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 4 Core
RAM: 4 GB
Disk: 80 GB
Installations: Kubernetes Control-Plane
CPU: 4 Core
RAM: 4 GB
Disk: 80 GB
Installations: Kubernetes Control-Plane
Server 3
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 4 Core
RAM: 4 GB
Disk: 80 GB
Installations: Kubernetes Control-Plane
CPU: 4 Core
RAM: 4 GB
Disk: 80 GB
Installations: Kubernetes Control-Plane
Kubernetes Worker Nodes
Server 4
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 12 Core
RAM: 16 GB
Disk: 80 GB
Installations: Kubernetes Worker
CPU: 12 Core
RAM: 16 GB
Disk: 80 GB
Installations: Kubernetes Worker
Server 5
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 12 Core
RAM: 16 GB
Disk: 80 GB
Installations: Kubernetes Worker
CPU: 12 Core
RAM: 16 GB
Disk: 80 GB
Installations: Kubernetes Worker
Server 6
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 12 Core
RAM: 16 GB
Disk: 80 GB
Installations: Kubernetes Worker
CPU: 12 Core
RAM: 16 GB
Disk: 80 GB
Installations: Kubernetes Worker
MongoDB Replica Set Nodes
Server 7
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 4 Core
RAM: 12 GB
Disk: 200 GB
Installations: MongoDB Replica Set Node 1
CPU: 4 Core
RAM: 12 GB
Disk: 200 GB
Installations: MongoDB Replica Set Node 1
Server 8
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 4 Core
RAM: 12 GB
Disk: 200 GB
Installations: MongoDB Replica Set Node 2
CPU: 4 Core
RAM: 12 GB
Disk: 200 GB
Installations: MongoDB Replica Set Node 2
Server 9
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 4 Core
RAM: 12 GB
Disk: 200 GB
Installations: MongoDB Replica Set Node 3
CPU: 4 Core
RAM: 12 GB
Disk: 200 GB
Installations: MongoDB Replica Set Node 3
Elasticsearch Cluster Nodes
Server 10
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 8 Core
RAM: 64 GB
Disk: 2 TB
Installations: Elasticsearch Cluster Node 1 (Master+Data)
CPU: 8 Core
RAM: 64 GB
Disk: 2 TB
Installations: Elasticsearch Cluster Node 1 (Master+Data)
Server 11
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 8 Core
RAM: 64 GB
Disk: 2 TB
Installations: Elasticsearch Cluster Node 2 (Master+Data)
CPU: 8 Core
RAM: 64 GB
Disk: 2 TB
Installations: Elasticsearch Cluster Node 2 (Master+Data)
Server 12
Operating System: Ubuntu Server 24.04 LTS / RHEL 9.x
CPU: 8 Core
RAM: 64 GB
Disk: 2 TB
Installations: Elasticsearch Cluster Node 3 (Master+Data)
CPU: 8 Core
RAM: 64 GB
Disk: 2 TB
Installations: Elasticsearch Cluster Node 3 (Master+Data)
Topology Comparison
| Feature | PoC / Test | Professional | High Available |
|---|---|---|---|
| Total Server Count | 2 | 3 | 12 |
| Kubernetes Control-Plane | 1 | 1 | 3 (HA) |
| Kubernetes Worker | 1 | 2 | 3 |
| MongoDB | Single Instance | Single Instance | Replica Set (3 nodes) |
| Elasticsearch | Single Node | Single Node | Cluster (3 nodes) |
| Usage Purpose | PoC, Test | Production | Production (HA) |
| High Availability | ❌ | ❌ | ✅ |
Topology Selection Guide
When Should PoC / Test Topology Be Used?
When Should PoC / Test Topology Be Used?
- Proof of Concept projects
- Development and test environments
- Low-traffic applications
- Quick installation requirements
- Limited resources
When Should Professional Topology Be Used?
When Should Professional Topology Be Used?
- Medium-scale production environments
- Medium-traffic applications
- Basic high availability requirements
- Budget optimization
When Should High Available Topology Be Used?
When Should High Available Topology Be Used?
- Critical production environments
- High-traffic applications
- High availability requirements (%99.9+)
- Data security and replication requirements
- Global distribution
Scaling Recommendations
Vertical Scaling
- CPU and RAM increase
- Disk capacity increase
- Increasing single server performance
Horizontal Scaling
- Increasing worker node count
- Increasing MongoDB replica set node count
- Increasing Elasticsearch cluster node count