Skip to content

Commit 451ae1e

Browse files
authored
Merge pull request #78468 from abrennan89/OSDOCS-9641
OSDOCS-9641: Scaled registry NFS docs
2 parents 2c889ea + 02e74d9 commit 451ae1e

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

modules/recommended-configurable-storage-technology.adoc

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
// Module included in the following assemblies:
22
//
3-
// * storage/optimizing-storage.adoc
43
// * post_installation_configuration/storage-configuration.adoc
4+
// * scalability_and_performance/optimization/optimizing-storage.adoc
55

6+
:_mod-docs-content-type: REFERENCE
67
[id="recommended-configurable-storage-technology_{context}"]
78
= Recommended configurable storage technology
89

@@ -93,6 +94,7 @@ In a non-scaled/high-availability (HA) {product-registry} cluster deployment:
9394
* The preferred storage technology is object storage followed by block storage.
9495
* File storage is not recommended for {product-registry} cluster deployment with production workloads.
9596
97+
[id="recommended-configurable-storage-technology-scaled-registry_{context}"]
9698
=== Scaled registry
9799
98100
In a scaled/HA {product-registry} cluster deployment:
@@ -104,6 +106,7 @@ In a scaled/HA {product-registry} cluster deployment:
104106
* Object storage should be S3 or Swift compliant.
105107
* For non-cloud platforms, such as vSphere and bare metal installations, the only configurable technology is file storage.
106108
* Block storage is not configurable.
109+
* The use of Network File System (NFS) storage with {product-title} is supported. However, the use of NFS storage with a scaled registry can cause known issues. For more information, see the Red{nbsp}Hat Knowledgebase solution, link:https://access.redhat.com/solutions/3428661[Is NFS supported for OpenShift cluster internal components in Production?].
107110
108111
=== Metrics
109112

0 commit comments

Comments
 (0)