| Both sides previous revision Previous revision | |
| dido:99_annexes:annex-b-terms-and-definitions:k:k3s [2026/08/04 07:08] – ↷ Links adapted because of a move operation nick_dido | 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 |
|---|
| 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. | 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:n: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. | 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. | 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. |