Skip to content

Commit 569deef

Browse files
committed
style: reformat new k3s content for easier readability
* break lines after 80 chars * add whites pace after . Signed-off-by: Jan Klare <[email protected]>
1 parent b4d9e94 commit 569deef

File tree

1 file changed

+22
-8
lines changed
  • docs/guides/concept-guide/components

1 file changed

+22
-8
lines changed
Lines changed: 22 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,31 @@
11
# K3s
22

3-
[K3s](https://k3s.io/) is a lightweight Kubernetes distribution designed for resource-constrained environments and edge computing. It is fully compliant with upstream Kubernetes, while offering significant simplifications to reduce operational overhead.
3+
[K3s](https://k3s.io/) is a lightweight Kubernetes distribution designed for
4+
resource-constrained environments and edge computing. It is fully compliant with
5+
upstream Kubernetes, while offering significant simplifications to reduce
6+
operational overhead.
47

5-
In OSISM contexts, K3s can serve as an alternative to full Kubernetes distributions like Kubernetes with Magnum or RKE2. Its minimal footprint makes it particularly suitable for testing, CI/CD runners, edge clusters, and bootstrapping control-plane components for infrastructure management.
8+
In OSISM contexts, K3s can serve as an alternative to full Kubernetes
9+
distributions like Kubernetes with Magnum or RKE2. Its minimal footprint makes
10+
it particularly suitable for testing, CI/CD runners, edge clusters, and
11+
bootstrapping control-plane components for infrastructure management.
612

713
## K3s main features
814

9-
- **Simple installation:** A small single binary with minimal setup. Swap out the binary, restart - no orchestration complexity.
10-
- **Reduced attack surface:** By stripping non-essential plugins and embedding TLS certificate management by default, K3s minimizes exposed vectors
11-
- **Less overhead**: Fewer components reduce complexity and operational friction in CI/CD pipelines and maintenance workflows.
12-
- **Built-in components:** Includes core add-ons like Helm controller, containerd, Traefik (optional), and local storage provisioner.
13-
- **Optimized for Edge:** Designed for low-resource environments and supports ARM, x86_64, and other CPU architectures.
15+
- **Simple installation:** A small single binary with minimal setup. Swap out
16+
the binary, restart - no orchestration complexity.
17+
- **Reduced attack surface:** By stripping non-essential plugins and embedding
18+
TLS certificate management by default, K3s minimizes exposed vectors
19+
- **Less overhead**: Fewer components reduce complexity and operational friction
20+
in CI/CD pipelines and maintenance workflows.
21+
- **Built-in components:** Includes core add-ons like Helm controller,
22+
containerd, Traefik (optional), and local storage provisioner.
23+
- **Optimized for Edge:** Designed for low-resource environments and supports
24+
ARM, x86_64, and other CPU architectures.
1425

15-
K3s shines not because it's tiny, but because it breaks down Kubernetes complexity.With K3s you can support **edge or remote clusters** where full Kubernetes is not practical, uniform Kubernetes experience across environments, and scale from dev to prod smoothly.
26+
K3s shines not because it's tiny, but because it breaks down Kubernetes
27+
complexity. With K3s you can support **edge or remote clusters** where full
28+
Kubernetes is not practical, uniform Kubernetes experience across environments,
29+
and scale from dev to prod smoothly.
1630

1731
## Lifecycle Management of K3S in OSISM

0 commit comments

Comments
 (0)