starlingx/docs
Code Issues Proposed changes

Missing information - "platform-integ-app" can not be applied if ceph is disabled (r8, ds8)

Browse Source 
Change-Id: I6b3c4973f46b077d0ff634e898b45407f772002a
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili
2023-08-22 06:55:25 +00:00
parent 0df05f304c
commit 6b76a0ccb2
1 changed files with 20 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
doc/source/storage/kubernetes/about-persistent-volume-support.rst
View File

@@ -9,33 +9,39 @@ About Persistent Volume Support
Persistent Volume Claims (PVCs) are requests for storage resources in your Persistent Volume Claims (PVCs) are requests for storage resources in your
cluster. By default, container images have an ephemeral file system. In order cluster. By default, container images have an ephemeral file system. In order
for containers to persist files beyond the lifetime of the container, a for containers to persist files beyond the lifetime of the container, a
Persistent Volume Claim can be created to obtain a persistent volume which the |PVC| can be created to obtain a persistent volume which the
container can mount and read/write files. container can mount and read/write files. In |prod-long|, |PVCs| are backed by
Ceph.
Management and customization tasks for Kubernetes |PVCs| Management and customization tasks for Kubernetes |PVCs|
can be accomplished by using StorageClasses set up by two Helm charts; can be accomplished by using StorageClasses set up by two Helm charts;
**rbd-provisioner** and **cephfs-provisioner**. The **rbd-provisioner**, ``rbd-provisioner`` and ``cephfs-provisioner``. The ``rbd-provisioner``,
and **cephfs-provisioner** Helm charts are included in the and ``cephfs-provisioner`` Helm charts are included in the
**platform-integ-apps** system application, which is automatically loaded and ``platform-integ-apps`` system application, which is automatically loaded and
applied as part of the |prod| installation. applied when Ceph is configured.
PVCs are supported with the following options: If ``platform-integ-apps`` is not applied, then enable Ceph. Enabling Ceph
would automatically apply the ``platform-integ-apps`` application. For
information on how to enable Ceph, see :ref:`Ceph Cluster on a Controller Host
<ceph-cluster-on-a-controller-host>`.
|PVCs| are supported with the following options:
- with accessMode of ReadWriteOnce backed by Ceph |RBD| - with accessMode of ReadWriteOnce backed by Ceph |RBD|
- only one container can attach to these PVCs - only one container can attach to these |PVCs|
- management and customization tasks related to these PVCs are done - management and customization tasks related to these PVCs are done
through the **rbd-provisioner** Helm chart provided by through the ``rbd-provisioner`` Helm chart provided by
platform-integ-apps ``platform-integ-apps``
- with accessMode of ReadWriteMany backed by CephFS - with accessMode of ReadWriteMany backed by CephFS
- multiple containers can attach to these PVCs - multiple containers can attach to these PVCs
- management and customization tasks related to these PVCs are done - management and customization tasks related to these |PVCs| are done
through the **cephfs-provisioner** Helm chart provided by through the ``cephfs-provisioner`` Helm chart provided by
platform-integ-apps ``platform-integ-apps``
After platform-integ-apps is applied the following system configurations are After ``platform-integ-apps`` is applied the following system configurations are
created: created:
- **Ceph Pools** - **Ceph Pools**