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||Keil MDK5 HTTP server - form input names||0 votes||79 views||0 replies||Started 11 days ago by Murilo Machado||Answer this|
|Not answered||Where to start with ARM Trust-zone development for Cortex-A series?||0 votes||76 views||0 replies||Started 12 days ago by J. Smith||Answer this|
|Not answered||ARM Debug Interface ADIv5||0 votes||90 views||0 replies||Started 16 days ago by Quasar||Answer this|
|Answered||Keil ARM Nuvoton Controller||0 votes||254 views||1 replies||Latest 22 days ago by Andy Neil||Answer this|
|Answered||giga byte value in normal convention for microcontroller use||0 votes||513 views||2 replies||Latest 1 months ago by fixxxer||Answer this|
|Answered||Keil 5.30 RTE defined automatically||0 votes||400 views||2 replies||Latest 1 months ago by fixxxer||Answer this|
|Not answered||Keil MDK5 HTTP server - form input names Started 11 days ago by Murilo Machado||0 replies 79 views|
|Not answered||Where to start with ARM Trust-zone development for Cortex-A series? Started 12 days ago by J. Smith||0 replies 76 views|
|Not answered||ARM Debug Interface ADIv5 Started 16 days ago by Quasar||0 replies 90 views|
|Answered||Keil ARM Nuvoton Controller Latest 22 days ago by Andy Neil||1 replies 254 views|
|Answered||giga byte value in normal convention for microcontroller use Latest 1 months ago by fixxxer||2 replies 513 views|
|Answered||Keil 5.30 RTE defined automatically Latest 1 months ago by fixxxer||2 replies 400 views|