Control Plane Cluster
The recommended default configuration for the Modernization Platform consists of a total of four Node Groups, as shown in the diagram below.
The specifications and quantity of Monitoring and Logging Nodes can be adjusted based on the volume and number of workloads running in the Data Plane Cluster.
The recommended specifications for each node are as follows.
AWS (vCPU * RAM) | Azure (vCPU * RAM * Disk) | |
|---|---|---|
Management Node | c5.2xlarge (8Core * 16GiB) | F8 (8Core * 16GiB * 128GiB) F8_v2 (8Core * 16GiB * 64GiB) |
Monitoring Node | m5.xlarge (4Core * 16GiB) Recommended for 3 or fewer Data Plane Clusters | D4_v3(4Core * 16GiB * 100GB) Recommended for 3 or fewer Data Plane Clusters |
r5.xlarge (4Core * 32GiB) Recommended for 4 or more Data Plane Clusters | D12_v2(4Core * 28GB * 200GB) Recommended for 4 or more Data Plane Clusters |
If the initial number of Data Plane Clusters is small and a Small Start approach is used, the Monitoring Node can be integrated into the Management Node as shown below. Once the number of Data Plane Clusters increases, the architecture can be quickly transitioned to the recommended default configuration.
In this case, the recommended specifications for each node are as follows.
AWS (vCPU * RAM) | Azure (vCPU * RAM * Disk) | |
|---|---|---|
Management & Monitoring Node | m5.2xlarge (8Core * 32GiB) | D8s_v3 (8Core * 32GiB * 64GiB) |
Logging Node | m5.xlarge (4Core * 16GiB) | D4_v3(4Core * 16GiB * 100GB) |
Edge Node | t3.medium (2Core * 4GiB) | B2s (2Core * 4GiB * 8 GiB, 1280 iops) F2s_v2(2Core * 4GiB * 16 GiB, 3200 iops) |
Management Node Group
The Management Node is a node where all components of the Modernization Platform, except for Monitoring/Logging/Edge-related components, are installed and operated (such as Console, MCM, IAM, CICD, etc.).
The Management Node Group consists of three nodes for availability.
Installed Components List
Console Web
IAM (KeyCloak)
CICD (Tekton, ArgoCD, Gitea, Harbor, Nexus)
Cert-Manager
Kubed
Back-end Components (Console, MCM, CICD, Monitoring, Logging, Harbor, ArgoCD)
Monitoring Node Group
The Monitoring Node is a node where service components for storing and visualizing all metrics of the Data Plane Cluster are installed and operated.
The Monitoring Node Group consists of three nodes for availability.
Installed Components List
Cortex
Grafana
Logging Node Group
The Logging Node is a node where service components for storing and visualizing all logs of the Data Plane Cluster are installed and operated.
The Logging Node Group consists of three nodes for availability.
Installed Components List
FluentD (for Receiver)
Elasticsearch Kibana
Elasticsearch Client & Master
Elasticsearch Data
Elasticsearch Curator
Edge Node Group
The Edge Node is a dedicated node where the Ingress NginX Controller component, which acts as the endpoint web server for the Modernization Platform, is installed and operated.
The Edge Node Group consists of two nodes for availability.
Installed Components List
Ingress NginX
Data Plane Cluster
The Data Plane Cluster's Node Group configuration can be constructed by creating each Node Group as shown in the diagram below, depending on workload requirements.
The recommended specifications for the Edge Node Group, which acts as the web server endpoint in each Managed Kubernetes Cluster, are as follows.
The number of Edge Node Groups can be architected with two or more nodes depending on the business nature of the workload.
AWS (vCPU * RAM) | Azure (vCPU * RAM * Disk) | |
|---|---|---|
Edge Node for Dev | t3.medium (2Core * 4GiB) | F2s_v2(2Core * 4GiB * 16 GiB, 3200 IOPS) |
Edge Node for Production | m5.xlarge (4Core * 16GiB) | D4_v3(4Core * 16GiB * 100GB) |
Online consultation
Contact us