Rancher is an enterprise computing platform that runs Kubernetes on-premises, in the cloud, on embedded Internet of Things (IoT) devices, in low-resource locations, on Arm, and at the edge.
Rancher addresses the operational and security challenges of managing multiple Kubernetes clusters everywhere. For Arm, Rancher provides IT operators and development teams with integrated tools for building, deploying, and running cloud-native workloads on Arm-based devices that run the Rancher lightweight Kubernetes distribution (K3s). K3s can scale complex, containerized workloads running at the edge on demand. All of this makes K3s ideal for enterprises exploring 5G, Citizens Broadband Radio System (CBRS) wireless, big data, artificial intelligence, and machine learning use cases on Arm.
Perfect for edge
K3s is available to Arm developers as a certified Kubernetes distribution. It is designed for production workloads in unattended, resource-constrained, remote locations, or inside IoT appliances.
Simplified and secure
K3s is packaged as a single, less than 40MB, binary that reduces the dependencies and steps needed to install, run, and auto-update a production Kubernetes cluster.
Optimized for Arm
Both Armv7 and AArch64 are supported with binaries and multi-architecture images. K3s is great for developers working across a wide range of Arm hardware, including embedded, edge devices, and the server space.
News and announcements
- Accelerating Edge Computing with Arm and Rancher k3s Lightweight Kubernetes
- Rancher Labs Introduces Lightweight Distribution of Kubernetes to Simplify Operations in Low-Resource Computing Environments
- Rancher Labs Introduces Lightweight Operating System for k3s to Improve Security for Kubernetes Operations
- Introducing k3s: The Lightweight Kubernetes Distribution Built for the Edge
- Rancher and Arm Partner to Accelerate Edge Computing
- How the Kubernetes community responded to the k3s launch
- Zero to k3s Kubeconfig in seconds with k3sup
- Easy Ingress Management on the Edge with K3s lightweight Kubernetes and Traefik
- Why K3s Is the Future of Kubernetes at the Edge
|Not answered||access secure generic timer||0 votes||68 views||0 replies||Started 7 days ago by armsss||Answer this|
|Not answered||How do branch instructions influence the performance of Cortex-A77?||0 votes||81 views||0 replies||Started 9 days ago by hyf_sysu||Answer this|
|Suggested answer||Getting Dummy character while receiving UART data,How to fix it ?||0 votes||455 views||2 replies||Latest 10 days ago by Jerome Decamps - 杜尚杰||Answer this|
|Suggested answer||Sht11 interfacing with lpc1758||0 votes||130 views||1 replies||Latest 14 days ago by Andy Neil||Answer this|
|Suggested answer||Arm Cortex A57 controller||0 votes||287 views||1 replies||Latest 15 days ago by Tyler_p||Answer this|
|Not answered||M7 to NIC-400 connectivity via AXIM||0 votes||87 views||0 replies||Started 20 days ago by Ramaswamy Vishwanath||Answer this|
|Not answered||access secure generic timer Started 7 days ago by armsss||0 replies 68 views|
|Not answered||How do branch instructions influence the performance of Cortex-A77? Started 9 days ago by hyf_sysu||0 replies 81 views|
|Suggested answer||Getting Dummy character while receiving UART data,How to fix it ? Latest 10 days ago by Jerome Decamps - 杜尚杰||2 replies 455 views|
|Suggested answer||Sht11 interfacing with lpc1758 Latest 14 days ago by Andy Neil||1 replies 130 views|
|Suggested answer||Arm Cortex A57 controller Latest 15 days ago by Tyler_p||1 replies 287 views|
|Not answered||M7 to NIC-400 connectivity via AXIM Started 20 days ago by Ramaswamy Vishwanath||0 replies 87 views|