The containers MAY ONLY be managed after appropriate planning.
This requirement must be implemented organizationally.
This planning MUST cover the entire life cycle from commissioning to decommissioning, including operation and updates.
This requirement must be implemented organizationally.
Through OpenShift GitOps, OpenShift technically supports this requirement with a standardized approach to deployment, change handling and deprovisioning via kustomize or Helm charts. OpenShift provides further support through operator-based applications and platform management that automates the processes of commissioning, decommissioning and updates.
When planning administration, it MUST be taken into account that the creator of a container should be viewed in part like an administrator due to the impact on operations.
This requirement must be implemented organizationally.
Starting, stopping and monitoring the containers MUST be done via the management software used.
Start, stop and monitoring is a basic function of OpenShift. It is not possible to bypass the OpenShift methods to start and stop. For monitoring purposes, OpenShift itself offers Prometheus-based monitoring. Using Advanced Cluster Security for Kubernetes (ACS), policy-based rules can also be used to monitor the containers.
organizationally only/inherently met