text: **Registry**
  OpenShift can build container images from source code, deploy them, and manage their 
  lifecycle. To enable this process, OpenShift provides an internal, integrated registry that can 
  be deployed in the OpenShift environment to manage images. 
  
  The registry stores images and metadata. For production environments, persistent storage 
  must be used for the registry; otherwise, any images that were built or pushed into the registry 
  disappear if the pod restarts. 
  
  **Aggregated logging**
  One of the Red Hat OpenShift Container Platform optional components is named Red Hat 
  OpenShift Container Platform aggregated logging. This component collects and aggregates 
  logs from the pods that are running in the Red Hat OpenShift Container Platform cluster and 
  /var/log/messages on nodes. This configuration enables Red Hat OpenShift Container 
  Platform users to view the logs of projects that they can view by using a web interface. 
  
  Red Hat OpenShift Container Platform aggregated logging component is a modified version 
  of the ELK stack, which is composed of a few pods that are running on the Red Hat OpenShift 
  Container Platform environment: 
  
  (cid:2) Elasticsearch: An object store where all logs are stored. 
  
  (cid:2) Kibana: A web UI for Elasticsearch. 
  
  (cid:2) Curator: Elasticsearch maintenance operations that are performed automatically on a 
  per-project basis. 
  
  (cid:2) Fluentd: Gathers logs from nodes and containers and feeds them to Elasticsearch. 