From e2a2a3a682fea7f399fa4649b62b5cf30928abf7 Mon Sep 17 00:00:00 2001
From: Lisa Durant <85700989+lisadurant@users.noreply.github.com>
Date: Tue, 12 Jul 2022 09:52:05 -0400
Subject: [PATCH] Update README.md

---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index cd2df83..c5bac4a 100644
--- a/README.md
+++ b/README.md
@@ -5,8 +5,9 @@ We provide Helm charts for two different deployment scenarios:
 See the [AWS Single-Instance Resiliency Chart](./https://github.com/sonatype/nxrm3-helm-repository/tree/main/aws-single-instance-resiliency) if you are doing the following:
 * Deploying Nexus Repository Pro to an AWS cloud environment with the desire for automatic failover across Availability Zones (AZs) within a single region
 * Planning to configure a single Nexus Repository Pro instance within your Kubernetes/EKS cluster with two or more nodes spread across different AZs within an AWS region
-* Using an external PostgreSQL database
+* Using an external PostgreSQL database (required)
 
 See the [Single-Instance OSS/Pro Kubernetes Chart](./https://github.com/sonatype/nxrm3-helm-repository/tree/main/single-inst-oss-pro-kubernetes) if you are doing the following:
+* Using embedded OrientDB (required)
 * Deploying either Nexus Repository Pro or OSS to an on-premises environment with bare metal/VM server (Node)
 * Deploying a single Nexus Repository instance within a Kubernetes cluster that has a single Node configured