Home > Communication Service Provider Solutions > Telecom Multicloud Foundation > Open Telecom Ecosystem > Guides > Certified Solution of SUSE Rancher 2.6.3, K3s 1.21.7 and SUSE Linux Enterprise Micro 5.1 on PowerEdge Servers > Solution architecture
SUSE Rancher Multi-Cluster Kubernetes Management run as a containerized application on a dedicated K3S HA cluster. K3S single node or multi-nodes can be deployed automatically using SUSE Rancher UI. Also, any K3S single node or K3S multi-node cluster or any CNCF-certified Kubernetes cluster can be imported to SUSE Rancher. SUSE Rancher can manage as many downstream K3S clusters as required. Modern Telecom containerized applications run on downstream K3S single node or multi-node clusters as shown in the figure below. There are different types of Telecom Features depending on the Modern Telecom containerized application type that is used, for more information on a sample of Telecom Features, see Appendix B. Testing and validation process is required based on the Modern Telecom containerized application of your choice. Please contact SUSE for more information.
Notes: Any platform that is SUSE YES certified can be used for the nodes of this deployment if the certification refers to the major version of the underlying SUSE operating system required by its release.
The following figure illustrates the high-level architecture of the SUSE Rancher installation that manages multiple downstream Kubernetes clusters:
The following table describes the components and functions of the SUSE Rancher solution:
Architecture | Function |
Authentication Proxy | An authentication proxy user is confirmed using SUSE Rancher. If the confirmation is approved, the user can access both the SUSE Rancher environment and the downstream clusters and workloads. |
API Server | The API Server provides the programmatic interface backend for a user who is using command-line interactions with SUSE Rancher and the managed clusters. |
Data Store | The Data Store captures the configuration and state of SUSE Rancher and the managed clusters that help in the backup and recovery processes. |
Cluster Controller | The Cluster Controller works with a cluster agent on the downstream cluster and leverages the communication path for users and services for workloads and cluster management. |
After the setup is complete, users can interact with SUSE Rancher through the web-based user interface (UI), the command-line interface (CLI), and, programmatically, through the application programming interface (API). Depending on the assigned roles, group membership, and privileges, users can:
Note: For optimal security and performance, SUSE recommends a dedicated Kubernetes cluster for the SUSE Rancher management server deployment.
CAUTION: Running user workloads on this cluster is not recommended. See the Rancher Architecture Recommendation page for more information.
After deploying SUSE Rancher, you can create or import clusters for orchestrated workloads, visit Setting up Kubernetes Cluster in Rancher web page.
For more information about K3S Architecture single node or multi-node, see the K3S Architecture page.