Skip to content

Commit

Permalink
Merge pull request #54677 from bburt-rh/RHDEVDOCS-4350-fix-for-monito…
Browse files Browse the repository at this point in the history
…ring-persistent-storage-requirements

RHDEVDOCS-4350-fix-for-monitoring-persistent-storage-requirements
  • Loading branch information
bburt-rh committed Jan 18, 2023
2 parents 1c3b6f2 + a801ceb commit 4deaf4e
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions modules/monitoring-configuring-persistent-storage.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ Running cluster monitoring with persistent storage means that your metrics are s

* Verify that you have a persistent volume (PV) ready to be claimed by the persistent volume claim (PVC), one PV for each replica. Because Prometheus and Alertmanager both have two replicas, you need four PVs to support the entire monitoring stack. The PVs are available from the Local Storage Operator, but not if you have enabled dynamically provisioned storage.

* Use the block type of storage.

* Use `Filesystem` as the storage type value for the `volumeMode` parameter when you configure the persistent volume.
+
[NOTE]
====
If you use a local volume for persistent storage, do not use a raw block volume, which is described with `volumeMode: block` in the `LocalVolume` object. Prometheus cannot use raw block volumes.
If you use a local volume for persistent storage, do not use a raw block volume, which is described with `volumeMode: Block` in the `LocalVolume` object. Prometheus cannot use raw block volumes.
====

0 comments on commit 4deaf4e

Please sign in to comment.