이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 1. Red Hat build of MicroShift storage overview
Red Hat build of MicroShift supports multiple types of storage, both for on-premise and cloud providers. You can manage container storage for persistent and non-persistent data in a Red Hat build of MicroShift cluster.
1.1. Storage types
Red Hat build of MicroShift storage is broadly classified into two categories, namely ephemeral storage and persistent storage.
1.1.1. 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. To read details about ephemeral storage, click Understanding ephemeral storage.
1.1.2. Persistent storage
Stateful applications deployed in containers require persistent storage. Red Hat build of MicroShift 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 persistent storage details, read Understanding persistent storage.
1.1.3. Dynamic storage provisioning
Using dynamic provisioning allows you to create storage volumes on-demand, eliminating the need for pre-provisioned storage. For more information about how dynamic provisioning works in Red Hat build of MicroShift, read Dynamic provisioning.
