+APP.4.4.A19 High Availability of Kubernetes (H)

APP.4.4.A19 High Availability of Kubernetes (H)

A Kubernetes operation SHOULD be set up in such a way that if a site fails, the clusters (and thus the applications in the pods) either continue to run without interruption or can be restarted in a short time at another site.

Should a restart be required, all the necessary configuration files, images, user data, network connections, and other resources required for operation (including the necessary hardware) SHOULD already be available at the alternative site.

For the uninterrupted operation of clusters, the control plane of Kubernetes, the infrastructure applications of the clusters, and the pods of the applications SHOULD be distributed across several fire zones based on the location data of the corresponding nodes so that the failure of a fire zone will not lead to the failure of an application.

1. Vue d’ensemble

Intitulé Norme

1.1 Références

1.2 Exigences identifiées

1.3 Réglementations associées

2. Exigences identifiées

Exigences
Source Exigence

3. Réglementations associées

Réglementations
Source Réglementation

Tickets liés

Liens
Type de lien Ticket
blocks G 0.25 Failure of Devices or Systems