[lucene-solr-operator] 01/01: Document what yaml keys to use for connectionInfo

[ja...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

janhoy pushed a commit to branch document-connectioninfo-keys
in repository https://gitbox.apache.org/repos/asf/lucene-solr-operator.git

commit 74e99267b5d7871783ed30fbdca20342853c38f3
Author: Jan Høydahl <ja...@users.noreply.github.com>
AuthorDate: Thu Feb 4 14:13:41 2021 +0100

    Document what yaml keys to use for connectionInfo
    
    To make it more clear
---
 docs/solr-cloud/solr-cloud-crd.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/docs/solr-cloud/solr-cloud-crd.md b/docs/solr-cloud/solr-cloud-crd.md
index 494879f..38ac130 100644
--- a/docs/solr-cloud/solr-cloud-crd.md
+++ b/docs/solr-cloud/solr-cloud-crd.md
@@ -91,6 +91,8 @@ The Solr operator gives a few options.
 - Connecting to an already running zookeeper ensemble via [connection strings](#zk-connection-info)
 - [Spinning up a provided](#provided-instance) Zookeeper Ensemble in the same namespace via the [Zookeeper Operator](https://github.com/pravega/zookeeper-operator)
 
+These options are configured under `spec.zookeeperRef`
+
 #### Chroot
 
 Both options below come with options to specify a `chroot`, or a ZNode path for solr to use as it's base "directory" in Zookeeper.
@@ -103,6 +105,12 @@ If a chroot is provided without a prefix of `/`, the operator will add the prefi
 This is an external/internal connection string as well as an optional chRoot to an already running Zookeeeper ensemble.
 If you provide an external connection string, you do not _have_ to provide an internal one as well.
 
+Under `spec.zookeeperRef`:
+
+- **`connectionInfo`**
+  - **`externalConnectionString`** - The ZK connection string to the external Zookeeper cluster, e.g. `zoo1:2181`
+  - **`chroot`** - The chroot to use for the cluster
+
 #### ACLs
 
 The Solr Operator allows for users to specify ZK ACL references in their Solr Cloud CRDs.