mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
Adds storage overview page
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
ee6d818195
commit
d5a6c73871
@@ -1156,6 +1156,9 @@ Name: Storage
|
||||
Dir: storage
|
||||
Distros: openshift-enterprise,openshift-origin,openshift-dedicated,openshift-online
|
||||
Topics:
|
||||
- Name: Storage overview
|
||||
File: index
|
||||
Distros: openshift-enterprise,openshift-origin,openshift-dedicated,openshift-online
|
||||
- Name: Understanding ephemeral storage
|
||||
File: understanding-ephemeral-storage
|
||||
Distros: openshift-enterprise,openshift-origin,openshift-dedicated,openshift-online
|
||||
|
||||
33
storage/index.adoc
Normal file
33
storage/index.adoc
Normal file
@@ -0,0 +1,33 @@
|
||||
[id="storage-overview"]
|
||||
= {product-title} storage overview
|
||||
include::modules/common-attributes.adoc[]
|
||||
:context: storage-overview
|
||||
|
||||
toc::[]
|
||||
|
||||
{product-title} supports multiple types of storage, both for on-premise and cloud providers. You can manage container storage for persistent and non-persistent data in an {product-title} cluster.
|
||||
|
||||
[id="storage-types"]
|
||||
== Storage Types
|
||||
|
||||
{product-title} storage is broadly classified into two categories, namely ephemeral storage and persistent storage.
|
||||
|
||||
[id="ephemeral-storage"]
|
||||
=== Ephemeral storage
|
||||
|
||||
Pods and containers are ephemeral or transient in nature and designed for stateless applications. Ephemeral storage allows administrators and developers to better manage the local storage for some of their operations. For more information about ephemeral storage overview, types, and management, see xref:../storage/understanding-ephemeral-storage.adoc#understanding-ephemeral-storage[Understanding ephemeral storage].
|
||||
|
||||
[id="persistent-storage"]
|
||||
=== Persistent storage
|
||||
|
||||
Stateful applications deployed in containers require persistent storage. {product-title} uses a pre-provisioned storage framework called persistent volumes (PV) to allow cluster administrators to provision persistent storage. The data inside these volumes can exist beyond the lifecycle of an individual pod. Developers can use persistent volume claims (PVCs) to request storage requirements. For more information about persistent storage overview, configuration, and lifecycle, see xref:../storage/understanding-persistent-storage.adoc#understanding-persistent-storage[Understanding persistent storage].
|
||||
|
||||
[id="container-storage-interface"]
|
||||
== Container Storage Interface (CSI)
|
||||
|
||||
CSI is an API specification for the management of container storage across different container orchestration (CO) systems. You can manage the storage volumes within the container native environments, without having specific knowledge of the underlying storage infrastructure. With the CSI, storage works uniformly across different container orchestration systems, regardless of the storage vendors you are using. For more information about CSI, see xref:../storage/container_storage_interface/persistent-storage-csi.adoc#persistent-storage-csi[Using Container Storage Interface (CSI)].
|
||||
|
||||
[id="dynamic-provisioning-overview"]
|
||||
== Dynamic Provisioning
|
||||
|
||||
Dynamic Provisioning allows you to create storage volumes on-demand, eliminating the need for cluster administrators to pre-provision storage. For more information about dynamic provisioning, see xref:../storage/dynamic-provisioning.adoc#dynamic-provisioning[Dynamic provisioning].
|
||||
Reference in New Issue
Block a user