Differences

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

--- public:99_annexes:annex-b-terms-and-definitions:k:k3s [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:k:k3s to public:99_annexes:annex-b-terms-and-definitions:k:k3s nick_dido
+++ public:99_annexes:annex-b-terms-and-definitions:k:k3s [2026/09/13 15:32] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== K3s ======
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 ===== Discussion =====
-K3s is a lightweight [[private:99_annexes:annex-b-terms-and-definitions:k:kubernetes]] distribution designed for resource-constrained, edge, remote, development, and production environments.
+K3s is a lightweight [[public: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 [[private: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 [[private:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[private:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[private:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns.
+In the Financial Systems [[public: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 [[public:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[public:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[public: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.
@@ Line 19: / Line 19: @@
 ===== Source =====
-Generalised from the official K3s documentation and K3s architecture description, and its use as a deployment concern in [[private:fxdemo:04-part:start]] and [[private: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.
+Generalised from the official K3s documentation and K3s architecture description, and its use as a deployment concern in [[private:01-fxdemo:04-part:start]] and [[private:01-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 =====