.``, e.g. ``ra2.ch.001`` for the first requirement in the Kubernetes Node section. These specifications will then be used as requirements input for the Kubernetes Reference Implementation and any vendor or community implementations. Figure 4-1 below shows the architectural components that are described in the subsequent sections of this chapter. .. raw:: html

Kubernetes Reference Architecture

Figure 4-1: Kubernetes Reference Architecture

Table 4-1: Node Specifications

Table 4-2: Kubernetes Specifications

Table 4-3: Container Runtime Specifications

Table 4-4: Networking Solution Specifications

Table 4-6: Storage Solution Specifications

A note on object storage: - This Reference Architecture does not include any specifications for object storage, as this is neither a native Kubernetes object, nor something that is required by CSI drivers. Object storage is an application-level requirement that would ordinarily be provided by a highly scalable service offering rather than being something an individual Kubernetes Cluster could offer. .. Todo: specifications/commentary to support req.inf.stg.04 (SDS) and req.inf.stg.05 (high performance and horizontally scalable storage). Also req.sec.gen.06 (storage resource isolation), req.sec.gen.10 (CIS - if applicable) and req.sec.zon.03 (data encryption at rest). .. _47-service-meshes: 4.7 Service meshes ------------------ Application service meshes are not in scope for the architecture. Network service mesh specifications are handled in section `4.5 Networking solutions <#45-networking-solutions>`__. .. _48-kubernetes-application-package-manager: 4.8 Kubernetes Application package manager ------------------------------------------ In order for the storage solution(s) to be conformant with the Reference Architecture they must be implemented as per the following specifications: +-------------+-------------+-------------+-------------+-------------+ | Ref | Sp | Details | Requirement | Reference | | | ecification | | Trace | Imp | | | | | | lementation | | | | | | Trace | +=============+=============+=============+=============+=============+ | ``ra | API-based | A package | `req.int. | | | 2.pkg.001`` | package | manager | api.02 <./c | | | | management | must use | hapter02.md | | | | | the | #23-kuberne | | | | | Kubernetes | tes-archite | | | | | APIs to | cture-requi | | | | | manage | rements>`__ | | | | | application | | | | | | artefacts. | | | | | | C | | | | | | luster-side | | | | | | components | | | | | | such as | | | | | | Tiller are | | | | | | not | | | | | | supported. | | | +-------------+-------------+-------------+-------------+-------------+ .. raw:: html

Table 4-7: Kubernetes Application Package Management Specifications

Table 4-8: Kubernetes Workload Specifications

.. _410-additional-required-components: 4.10 Additional required components ----------------------------------- This chapter should list any additional components needed to provide the services defined in Chapter 3.2 (e.g: Prometheus)