Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:k:k3s [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:99_annexes:annex-b-terms-and-definitions:k:k3s [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== K3s ======
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+===== Discussion =====
+K3s is a lightweight [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes]] distribution designed for resource-constrained, edge, remote, development, and production environments.
+K3s packages Kubernetes control-plane operation into a simplified distribution with reduced external dependencies. K3s uses a server-and-agent architecture: a server node runs control-plane and datastore components managed by K3s, while an agent node runs without datastore or control-plane components. Both server and agent nodes run the kubelet, container runtime, and container networking interface.
+In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, K3s belongs to implementation, deployment, and runtime-infrastructure concerns. K3s does not define logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns.
+An implementation profile maps selected logical Nodes, communication responsibilities, configuration concerns, observability concerns, and deployment concerns to K3s resources when K3s serves as the selected Kubernetes distribution.
+===== Definition =====
+//lightweight Kubernetes distribution used to deploy, operate, and manage containerised workloads in resource-constrained, edge, remote, development, or production environments//
+===== Source =====
+Generalised from the official K3s documentation and K3s architecture description, and its use as a deployment concern in [[fxdemo:04-part:start]] and [[fxdemo:05-part:start]]. K3s describes itself as a certified Kubernetes distribution for production workloads in unattended, resource-constrained, remote, IoT, and edge environments. Its architecture defines server nodes and agent nodes, with both running kubelet, container runtime, and container networking interface components.
+===== Note =====
+K3s is not Kubernetes itself, a logical Node, logical Communication Endpoint, Runtime Plane, DDS Domain, DDS Topic, message bus, data structure, governance model, evidence model, or architecture layer.
+===== Example =====
+Part 5 uses K3s as an optional deployment target for running containerised Phase 0 nodes after the logical Nodes and logical Communication Endpoints have already been defined in platform-independent form.