|Index|SUSE Telco Cloud Documentation|Concept & Architecture|Components

2 Components

There are two different blocks, the management stack and the runtime stack:

  • Management stack: This is the part of SUSE Telco Cloud that is used to manage the provision and lifecycle of the runtime stacks. It includes the following components:

    • Multi-cluster management in public and private cloud environments with Rancher (Chapter 6, Rancher)

    • Bare-metal support with Metal3 (Chapter 11, Metal3), MetalLB (Chapter 17, MetalLB) and CAPI (Cluster API) infrastructure providers

    • Comprehensive tenant isolation and IDP (Identity Provider) integrations

    • Large marketplace of third-party integrations and extensions

    • Vendor-neutral API and rich ecosystem of providers

    • Control the SUSE Linux Micro transactional updates

    • GitOps Engine for managing the lifecycle of the clusters using Git repositories with Fleet (Chapter 9, Fleet)

  • Runtime stack: This is the part of SUSE Telco Cloud that is used to run the workloads.

    • RKE2 (Chapter 14, RKE2) serves as the security-hardened, lightweight Kubernetes distribution, optimized for edge and compliance-focused telecom environments.

    • (Optional) SUSE Security (Chapter 16, SUSE Security) to enable security features like image vulnerability scanning, deep packet inspection and automatic intra-cluster traffic control.

    • (Optional) Block Storage with SUSE Storage (Chapter 15, SUSE Storage) to enable a simple and easy way to use a cloud native storage solution.

    • Optimized Operating System with SUSE Linux Micro (Chapter 10, SUSE Linux Micro) to enable a secure, lightweight and immutable (transactional file system) OS for running containers. SUSE Linux Micro is available on AArch64 and AMD64/Intel 64 architectures, and it also supports Real-Time Kernel for Telco and edge use cases.