Skip to main content

RKE2

RKE2 (also known as RKE Government) is a Kubernetes distribution (container orchestration) from SUSE designed for automated, standards-aligned cluster installation and lifecycle management across on-premises (on-prem), air-gapped, and cloud environments.

  • Kubernetes distribution with automated install and lifecycle management (container orchestration).
  • Validated and hardened deployment model for security-focused and regulated environments (security and compliance).
  • Supports air-gapped, disconnected, and edge deployments with mirrored registries and offline artifacts (edge and offline operations).
  • Integrates with standard Kubernetes tooling and APIs for workloads, networking, and storage (cloud-native platform).
  • Operates alongside SUSE Rancher for multi-cluster management and governance (platform management).

More About RKE2

RKE2 is a Kubernetes distribution (container orchestration) from SUSE that addresses installation, security posture, and lifecycle management requirements for enterprises that run Kubernetes in regulated, security-sensitive, or operationally constrained environments. It is also referred to in SUSE documentation as “RKE Government,” indicating a focus on use cases that require controlled supply chains, predictable behavior, and adherence to published security guidance.

The project targets the problem space of installing and operating Kubernetes clusters in a standardized way across heterogeneous infrastructure, including on-prem data centers, virtualized platforms, bare metal, and public cloud. RKE2 packages the Kubernetes Control Plane (KCP) and node components with a curated set of defaults (platform engineering) that follow documented hardening and configuration guidance. The distribution is designed so that cluster provisioning, upgrades, and configuration can be automated and expressed as Infrastructure-as-Code (IaC) using existing automation frameworks in the enterprise.

RKE2 exposes the standard Kubernetes Application Programming Interface (API) and resource model (cloud-native platform), so platform and application teams can use familiar tools such as kubectl, Helm, and GitOps workflows for workload deployment, networking, and storage integration. The distribution supports deployment into air-gapped or disconnected environments (edge and offline operations) by using mirrored container registries and locally hosted installation artifacts, which is a common requirement in government and industrial networks. Documentation describes how to stage images and RPMs or other packages into restricted environments so that clusters can be installed and upgraded without direct internet access.

In enterprise environments, RKE2 is commonly paired with SUSE Rancher (platform management), which provides centralized cluster inventory, access control, policy management, and observability across multiple RKE2 and other Kubernetes clusters. This combination enables operations teams to maintain a consistent cluster baseline while platform teams consume Kubernetes as a shared service. RKE2 also aligns with standard Kubernetes networking and storage interfaces such as Container Network Interface (CNI) and Critical Supplier Identification (CSI) (infrastructure integration), enabling integration with enterprise network plugins, load balancers, and storage backends documented as compatible with the distribution.

From a categorization perspective, RKE2 fits into the Kubernetes distribution and container orchestration category within cloud-native infrastructure platforms. It is relevant for organizations that need a maintained, installable Kubernetes distribution with documented security posture, air-gapped support, and integration paths into existing automation, observability, and access control systems, particularly where regulatory or internal policy requirements govern how clusters are built and maintained.