---
type: "ABB"
nummer: "ABB-0418"
abb_id: "ABB-0418"
abb_nummer: "Niet vermeld"
naam: "Worker Node"
archimate_type: "Grouping"
laag: "Basisfunctionaliteit"
auteur: "Niet vermeld"
status: "Niet vermeld"
gerelateerde_adrs: []
archimate_element: "id-30480"
archimate_grouping: "id-30480"
archimate_technology_service: ["id-30301"]
archimate_view: "id-29983"
ontwerp_paragraaf: "5.4.2"
ontwerp_link: "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-nodes"
ontwerp_paragrafen: ["5.4.2", "5.4.3"]
ontwerp_links:
  - "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-nodes"
  - "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-abb-tenant-cluster"
---

# ABB-0418: Worker Node

```mermaid
%%{init: {"flowchart": {"nodeSpacing": 12, "rankSpacing": 12, "padding": 8}}}%%
flowchart TB
    %% id-30816 -> id-30480 (Grouping)
    subgraph v_id_30816["ABB: Worker Node"]
        direction TB
        %% id-30817 -> id-30301 (TechnologyService)
        v_id_30817["Worker Node"]
    end
    %% id-30818 -> id-30566 (Grouping)
    subgraph v_id_30818["ABB: Master Node"]
        direction TB
        %% id-30819 -> id-30307 (TechnologyService)
        v_id_30819["Master Node"]
    end
    %% id-30811 -> id-30580 (Grouping)
    subgraph v_id_30811["ABB: General Purpose Worker Node"]
        direction TB
        %% id-30812 -> id-30303 (TechnologyService)
        v_id_30812["General Purpose Worker Node"]
    end
    %% id-30808 -> id-30809 (Grouping)
    subgraph v_id_30808["ABB: Accelerated Worker Node"]
        direction TB
        %% id-30810 -> id-30328 (TechnologyService)
        v_id_30810["Accelerated Worker Node"]
    end
    %% id-30803 -> id-30785 (Grouping)
    subgraph v_id_30803["ABB: General Purpose Bare-Metal"]
        direction TB
        %% id-30804 -> id-30643 (TechnologyService)
        v_id_30804["General Purpose Bare-Metal"]
    end
    %% id-30806 -> id-30780 (Grouping)
    subgraph v_id_30806["ABB: Accelerated Bare-Metal"]
        direction TB
        %% id-30807 -> id-30647 (TechnologyService)
        v_id_30807["Accelerated Bare-Metal"]
    end
    v_id_30804 -->|Serving| v_id_30819
    v_id_30804 -->|Serving| v_id_30812
    v_id_30807 -->|Serving| v_id_30810
    v_id_30812 -->|Specialization| v_id_30817
    v_id_30810 -->|Specialization| v_id_30817
    style v_id_30817 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30816 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30819 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30818 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30812 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30811 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30810 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30808 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30804 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30803 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30807 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30806 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
```

## Positionering Nodes

De Kubernetes Master Node is altijd gebaseerd op algemeen-inzetbare hardware. Voor Worker Nodes kan naar keuze eventueel ook opgevoerde hardware worden ingezet.

![Figuur 5‑15 Positionering Nodes](<../../input/markdown/media/media/image39.svg>)

## Positionering ABB "Tenant Cluster"

Elk Tenant Cluster bestaat uit Worker Nodes met eigen hardware. De Kubernetes control plan van elk Tenant Cluster maakt wel gebruik van gedeelde hardware (Hosted Control Plane).

![Figuur 5‑16 Positionering ABB Tenant Cluster](<../../input/markdown/media/media/image41.svg>)

Samenvatting uitgangspunten, architectuurkeuzes en aandachtspunten:

- De afnemer kan één of meerdere tenantclusters afnemen die zowel onderling als van tenantclusters van andere afnemers fysiek gescheiden zijn;

- Elke tenantcluster kan logisch verder opgedeeld worden in projecten die elk weer bestaan uit Kubernetes namespaces.
