System Requirements

Objective

This guide explains how to use System Requirements on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

PackageKubernetes ClusterMay not be available in some areas.regionsThis is due to the platform-specific hardware. In this case, please contact your hosting provider's support.

The minimum and optimal RAM, CPU, and storage usage depends on the cluster size, installed components, active workload, etc.

Note:

• [1]Measurements were performed on bare development and production clusters without any additional load, so the values given are the minimum system requirements, which can be much higher for loaded clusters (especially for production).
• [2]Development cluster topology – one master, one worker, one storage node There is no sample deployment verification tool for Hello World.
• [3]Production cluster topology - API balancer, three masters, two workers, one storage node, monitoring tools, deployment example for Hello World
• [4]A fast disk is critical to the performance of etcd (key-value store used by K8s), while a slow etcd can make the cluster unstable due to workload failure.

Learn more:Disk Requirements,Benchmark Information,How to Run Benchmark, andDownload Benchmark

It is recommended to use the development cluster as a sandbox environment only. For production purposes, a highly available topology with multi-master is the preferred option. Then, depending on the expected load, the required number of workers can be increased manually or can be determined.automatic horizontal scalingAdding additional master nodes is only appropriate if there is a high volume of requests coming from clients (kubectl, dashboard, continuous integration jobs, K8s-native applications, etc.).