---
type: "ABB"
nummer: "ABB-0408"
abb_id: "ABB-0408"
abb_nummer: "Niet vermeld"
naam: "Tenant Cluster Container Connectivity"
archimate_type: "Grouping"
laag: "Basisfunctionaliteit"
auteur: "Niet vermeld"
status: "Niet vermeld"
gerelateerde_adrs: []
archimate_element: "id-30697"
archimate_grouping: "id-30697"
archimate_technology_service: ["id-30322"]
archimate_view: "id-29980"
ontwerp_paragraaf: "5.4.3"
ontwerp_link: "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-abb-tenant-cluster"
ontwerp_paragrafen: ["5.4.3"]
ontwerp_links: ["../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-abb-tenant-cluster"]
---

# ABB-0408: Tenant Cluster Container Connectivity

```mermaid
%%{init: {"flowchart": {"nodeSpacing": 12, "rankSpacing": 12, "padding": 8}}}%%
flowchart TB
    %% id-30687 -> id-30221 (Grouping)
    subgraph v_id_30687["ABB: Tenant Cluster Data Plane-as-a-Service"]
        direction TB
        %% id-30688 -> id-30222 (TechnologyService)
        v_id_30688["Tenant Cluster Data Plane-as-a-Service"]
        %% id-30689 -> id-30690 (Grouping)
        subgraph v_id_30689["ABB: Tenant Cluster Container Runtime"]
            direction TB
            %% id-30691 -> id-30324 (TechnologyService)
            v_id_30691["Tenant Cluster Container Runtime"]
        end
        %% id-30696 -> id-30697 (Grouping)
        subgraph v_id_30696["ABB: Tenant Cluster Container Connectivity"]
            direction TB
            %% id-30698 -> id-30322 (TechnologyService)
            v_id_30698["Tenant Cluster Container Connectivity"]
        end
        %% id-30693 -> id-30694 (Grouping)
        subgraph v_id_30693["ABB: Tenant Cluster Container Storage"]
            direction TB
            %% id-30695 -> id-30326 (TechnologyService)
            v_id_30695["Tenant Cluster Container Storage"]
        end
    end
    v_id_30688 -->|Composition| v_id_30691
    v_id_30688 -->|Composition| v_id_30698
    v_id_30688 -->|Composition| v_id_30695
    style v_id_30688 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30691 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30689 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30698 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30696 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30695 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30693 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30687 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
```

## 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.
