| Both sides previous revision Previous revision | |
| dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes [2026/08/04 07:08] – ↷ Links adapted because of a move operation nick_dido | dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| Kubernetes groups containerised workloads into deployable and manageable units and provides mechanisms for scheduling, service discovery, scaling, rollout, recovery, configuration, secret management, and workload lifecycle management. | Kubernetes groups containerised workloads into deployable and manageable units and provides mechanisms for scheduling, service discovery, scaling, rollout, recovery, configuration, secret management, and workload lifecycle management. |
| |
| In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, Kubernetes belongs to implementation, deployment, and runtime-infrastructure concerns. Kubernetes 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, Kubernetes belongs to implementation, deployment, and runtime-infrastructure concerns. Kubernetes 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, deployment concerns, and operational concerns to Kubernetes resources when Kubernetes serves as the selected orchestration platform. | An implementation profile maps selected logical Nodes, communication responsibilities, configuration concerns, observability concerns, deployment concerns, and operational concerns to Kubernetes resources when Kubernetes serves as the selected orchestration platform. |