Don't provide zookeeper-refdb plugin in container

The zookeeper-refdb plugin is not being maintained anymore in
opensource. Users can still use it by manually building it into
the container or providing a download URL in the CR.

Change-Id: I43d9a3cabe9688ba2bc5e56265a6651ebcd946c6

Documentation/examples/5-gerritcluster-refdb.yaml

diff --git a/Documentation/examples/5-gerritcluster-refdb.yaml b/Documentation/examples/5-gerritcluster-refdb.yaml
index 5091f27..5f073fa 100644
--- a/Documentation/examples/5-gerritcluster-refdb.yaml
+++ b/Documentation/examples/5-gerritcluster-refdb.yaml
@@ -90,6 +90,9 @@
       # This way plugins are installed from the Gerrit-war file
       - name: download-commands
       - name: delete-project
+      - name: zookeeper-refdb
+        url:
+        sha1:
 
       configFiles:
         # Some configuration options are specific to the k8sgerrit setup. These

Documentation/examples/6-gerritcluster-ha-primary.yaml

diff --git a/Documentation/examples/6-gerritcluster-ha-primary.yaml b/Documentation/examples/6-gerritcluster-ha-primary.yaml
index 1dd0dc3..9bdfb3d 100644
--- a/Documentation/examples/6-gerritcluster-ha-primary.yaml
+++ b/Documentation/examples/6-gerritcluster-ha-primary.yaml
@@ -92,6 +92,9 @@
       # This way plugins are installed from the Gerrit-war file
       - name: download-commands
       - name: delete-project
+      - name: zookeeper-refdb
+        url:
+        sha1:
 
       configFiles:
         # Some configuration options are specific to the k8sgerrit setup. These

Documentation/operator.md

diff --git a/Documentation/operator.md b/Documentation/operator.md
index eac3b6d..93d9206 100644
--- a/Documentation/operator.md
+++ b/Documentation/operator.md
@@ -635,7 +635,10 @@
 helm upgrade --install zookeeper oci://registry-1.docker.io/bitnamicharts/zookeeper -n zookeeper
 ```
 
-Now, the GerritCluster can be configured to use the Global RefDB
+Now, the GerritCluster can be configured to use the Global RefDB. Since the
+zookeeper plugin is not maintained in the opensource project at the moment,
+configure a URL from where to download the plugin in `Documentation/examples/5-gerritcluster-refdb.yaml`.
+Then run:
 
 ```sh
 diff Documentation/examples/4-gerritcluster-ha-replica.yaml Documentation/examples/5-gerritcluster-refdb.yaml
@@ -654,8 +657,8 @@
 kubectl apply -f Documentation/examples/gerrit.rbac.yaml
 ```
 
-Now, the primary Gerrit can be scaled up. The ServiceAccount also has to be
-referenced:
+Now, the primary Gerrit can be scaled up (Don't forget to also add the
+zookeeper-refdb plugin URL). The ServiceAccount also has to be referenced:
 
 ```sh
 diff Documentation/examples/5-gerritcluster-refdb.yaml Documentation/examples/6-gerritcluster-ha-primary.yaml

container-images/gerrit-base/Dockerfile

diff --git a/container-images/gerrit-base/Dockerfile b/container-images/gerrit-base/Dockerfile
index c9d8035..be6fa77 100644
--- a/container-images/gerrit-base/Dockerfile
+++ b/container-images/gerrit-base/Dockerfile
@@ -34,10 +34,6 @@
 ARG HA_JAR_URL=https://gerrit-ci.gerritforge.com/job/plugin-high-availability-bazel-${GERRIT_BRANCH}/lastSuccessfulBuild/artifact/bazel-bin/plugins/high-availability/high-availability.jar
 RUN curl -f -k -o /var/plugins/high-availability.jar ${HA_JAR_URL}
 
-# Download zookeeper-refdb plugin
-ARG ZOOKEEPER_REFDB_URL=https://gerrit-ci.gerritforge.com/job/plugin-zookeeper-refdb-bazel-${GERRIT_BRANCH}/lastSuccessfulBuild/artifact/bazel-bin/plugins/zookeeper-refdb/zookeeper-refdb.jar
-RUN curl -f -k -o /var/plugins/zookeeper-refdb.jar ${ZOOKEEPER_REFDB_URL}
-
 # Download spanner-refdb plugin
 ARG SPANNER_REFDB_URL=https://gerrit-ci.gerritforge.com/job/plugin-spanner-refdb-bazel-master-${GERRIT_BRANCH}/lastSuccessfulBuild/artifact/bazel-bin/plugins/spanner-refdb/spanner-refdb.jar
 RUN curl -f -k -o /var/plugins/spanner-refdb.jar ${SPANNER_REFDB_URL}