sdap-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [incubator-sdap-nexus] branch bug_fixes updated: Readme
Date Thu, 03 Dec 2020 20:03:34 GMT
This is an automated email from the ASF dual-hosted git repository.

eamonford pushed a commit to branch bug_fixes
in repository

The following commit(s) were added to refs/heads/bug_fixes by this push:
     new 470ee79  Readme
470ee79 is described below

commit 470ee7994cc5318d4223d9c07fec806b1c122f52
Author: Eamon Ford <>
AuthorDate: Thu Dec 3 12:03:10 2020 -0800

 helm/ | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/helm/ b/helm/
index f206b24..529472f 100644
--- a/helm/
+++ b/helm/
@@ -28,7 +28,6 @@ The helm chart deploys all the required components of the NEXUS application
     - [Ingress Parameters](#ingress-parameters)
   - [Restricting Pods to Specific Nodes](#restricting-pods-to-specific-nodes)
   - [Notes about Persistent Volume Storage Classes](#notes-about-persistent-volume-storage-classes)
-      - [Example](#example)
 ## Prerequisites
@@ -333,7 +332,9 @@ solr:
 The SDAP Helm chart uses [persistent volumes](
for RabbitMQ, Solr, Zookeeper, Cassandra, and optionally the Collection Manager ingestion
component (if Solr ingestion history is disabled).
 In most use cases you will want to use the same storage class for all of these components.
-#### Example 
 If you are deploying SDAP on AWS and you want to use
 [EBS GP2](
volumes for persistence storage, you would need to use the following configuration values
for the SDAP Helm chart:

View raw message