Postinstallation storage configuration¶
You can configure persistent storage after installation by using dynamic or static provisioning to retain application data beyond the lifetime of individual containers.
After installing OpenShift Container Platform, you can further expand and customize your cluster to your requirements, including storage configuration.
By default, containers operate by using the ephemeral storage or transient local storage. The ephemeral storage has a lifetime limitation. To store the data for a long time, you must configure persistent storage. You can configure storage by using one of the following methods:
- Dynamic provisioning
- You can dynamically provision storage on-demand by defining and creating storage classes that control different levels of storage, including storage access.
- Static provisioning
- You can use Kubernetes persistent volumes to make existing storage available to a cluster. Static provisioning can support various device configurations and mount options.
Dynamic provisioning¶
Dynamic provisioning allows you to create storage volumes on-demand, eliminating the need for cluster administrators to pre-provision storage.
Recommended configurable storage technology¶
Review the recommended and configurable storage technologies for the given OpenShift Container Platform cluster application.
Recommended and configurable storage technology
| Storage type | Block | File | Object |
|---|---|---|---|
| ROX | Yes | Yes | Yes |
| RWX | No | Yes | Yes |
| Registry | Configurable | Configurable | Recommended |
| Scaled registry | Not configurable | Configurable | Recommended |
| Metrics | Recommended | Configurable | Not configurable |
| Elasticsearch Logging | Recommended | Configurable | Not supported |
| Loki Logging | Not configurable | Not configurable | Recommended |
| Apps | Recommended | Recommended | Not configurable |
where:
ROX- Specifies
ReadOnlyManyaccess mode. ROX.Yes- Specifies that this access mode
RWX- Specifies
ReadWriteManyaccess mode. Metrics- Specifies Prometheus as the underlying technology used for metrics.
Metrics.Configurable- For metrics, using file storage with the
ReadWriteMany(RWX) access mode is unreliable. If you use file storage, do not configure the RWX access mode on any persistent volume claims (PVCs) that are configured for use with metrics. Elasticsearch Logging.Configurable- For logging, review the recommended storage solution in Configuring persistent storage for the log store section. Using NFS storage as a persistent volume or through NAS, such as Gluster, can corrupt the data. Therefore, NFS is not supported for Elasticsearch storage and LokiStack log store in OpenShift Container Platform Logging. You must use one persistent volume type per log store.
Apps.Not configurable- Specifies that object storage is not consumed through PVs or PVCs of OpenShift Container Platform. Apps must integrate with the object storage REST API.
Note
A scaled registry is an OpenShift image registry where two or more pod replicas are running.
Deploy Red Hat OpenShift Data Foundation¶
Red Hat OpenShift Data Foundation is a provider of agnostic persistent storage for OpenShift Container Platform supporting file, block, and object storage, either in-house or in hybrid clouds.
As a Red Hat storage solution, Red Hat OpenShift Data Foundation is completely integrated with OpenShift Container Platform for deployment, management, and monitoring.
Warning
OpenShift Data Foundation on top of Red Hat Hyperconverged Infrastructure (RHHI) for Virtualization, which uses hyperconverged nodes that host virtual machines installed with OpenShift Container Platform, is not a supported configuration. For more information about supported platforms, see the Red Hat OpenShift Data Foundation Supportability and Interoperability Guide.
| If you are looking for Red Hat OpenShift Data Foundation information about... | See the following Red Hat OpenShift Data Foundation documentation: |
|---|---|
| What’s new, known issues, notable bug fixes, and Technology Previews | OpenShift Data Foundation 4.12 Release Notes |
| Supported workloads, layouts, hardware and software requirements, sizing and scaling recommendations | Planning your OpenShift Data Foundation 4.12 deployment |
| Instructions on deploying OpenShift Data Foundation to use an external Red Hat Ceph Storage cluster | Deploying OpenShift Data Foundation 4.12 in external mode |
| Instructions on deploying OpenShift Data Foundation to local storage on bare metal infrastructure | Deploying OpenShift Data Foundation 4.12 using bare metal infrastructure |
| Instructions on deploying OpenShift Data Foundation on Red Hat OpenShift Container Platform VMware vSphere clusters | Deploying OpenShift Data Foundation 4.12 on VMware vSphere |
| Instructions on deploying OpenShift Data Foundation using Amazon Web Services for local or cloud storage | Deploying OpenShift Data Foundation 4.12 using Amazon Web Services |
| Instructions on deploying and managing OpenShift Data Foundation on existing Red Hat OpenShift Container Platform Google Cloud clusters | Deploying and managing OpenShift Data Foundation 4.12 using Google Cloud |
| Instructions on deploying and managing OpenShift Data Foundation on existing Red Hat OpenShift Container Platform Azure clusters | Deploying and managing OpenShift Data Foundation 4.12 using Microsoft Azure |
| Instructions on deploying OpenShift Data Foundation to use local storage on IBM Power(R) infrastructure | Deploying OpenShift Data Foundation on IBM Power(R) |
| Instructions on deploying OpenShift Data Foundation to use local storage on IBM Z(R) infrastructure | Deploying OpenShift Data Foundation on IBM Z(R) infrastructure |
| Allocating storage to core services and hosted applications in Red Hat OpenShift Data Foundation, including snapshot and clone | Managing and allocating resources |
| Managing storage resources across a hybrid cloud or multicloud environment using the Multicloud Object Gateway (NooBaa) | Managing hybrid and multicloud resources |
| Safely replacing storage devices for Red Hat OpenShift Data Foundation | Replacing devices |
| Safely replacing a node in a Red Hat OpenShift Data Foundation cluster | Replacing nodes |
| Scaling operations in Red Hat OpenShift Data Foundation | Scaling storage |
| Monitoring a Red Hat OpenShift Data Foundation 4.12 cluster | Monitoring Red Hat OpenShift Data Foundation 4.12 |
| Resolve issues encountered during operations | Troubleshooting OpenShift Data Foundation 4.12 |
| Migrating your OpenShift Container Platform cluster from version 3 to version 4 | Migration |
Additional resources