Home > Workload Solutions > Container Platforms > SUSE Containers as a Service > Guides > Certified Solution of SUSE Rancher, K3s, and SUSE Linux Enterprise Micro Using Dell PowerEdge Servers > Solution architecture
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.
After deploying SUSE Rancher, you can create or import clusters for orchestrated workloads.