The following diagram shows logical architecture diagram of the RKE cluster deployed on a two-layer PowerFlex cluster setup with four storage-only nodes and three compute-only nodes.
Figure 3 Logical architecture
In this example, each storage-only node includes two Intel® Xeon® Scalable 12-core processors, 224 GB RAM, and eight 1.92 TB SSDs. From the PowerFlex (previously VxFlex OS) standpoint, the Embedded OS storage only nodes run the SDS component of PowerFlex to provide storage capacity. A single protection domain is created from these four SDS systems. A single storage pool is created within this protection domain from which persistent storage volumes can be provisioned for attachment to Kubernetes pods. The PowerFlex SDC component is installed into the VMware ESXi 7.x hypervisor running on the three Compute Only nodes, this provides access to volumes created within the storage pool.
In this solution, each of the virtual machines are installed with SLES15 SP2 operating system. The RKE cluster is deployed in virtual machines on a VMware vSphere 7.0 cluster. For SUSE Rancher to work, the minimum hardware requirement to run Kubernetes node components is one CPU and 1 GB of memory. Considering CPU and Memory, it is recommended to host the different roles of the Kubernetes cluster (etcd, control plane, and workers) on different nodes so that they can scale independently from one another. In this solution, each virtual machine is configured with 2 virtual CPUs, 8 GB RAM, and thick provisioned disks on the PowerFlex backend storage.
The management node hosts the vCenter appliance, PowerFlex Gateway, PowerFlex Presentation Server, Repository Mirroring Tool (RMT) server, and Linux workstation for RKE. The RMT server and Linux workstation are virtual machines configured with SLES15 SP2 operating system. The RMT server acts as a proxy server to SUSE Customer Center with repositories. It helps customers with SUSE Linux Enterprise software updates and subscription entitlements. For more information about RMT server and its configuration, see .