Bump Bitnami Chart, ZK Tag, and Update Docs (#93)

* Bump Bitnami Chart version to 8.1.2
* Bump ZK image tag to 3.7.1
* Add documentation for upgrading Zookeeper

README.md

@@ -2,7 +2,7 @@ Stardog Helm Charts
 ===================
 
 [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
-[![<ORG_NAME>](https://circleci.com/gh/stardog-union/helm-charts.svg?style=shield&circle-token=213cf9bca0acf5d3945dfd5d746b48f1c2d436e0)](https://app.circleci.com/pipelines/gh/stardog-union/helm-charts)
+[![stardog-union](https://circleci.com/gh/stardog-union/helm-charts.svg?style=shield)](https://app.circleci.com/pipelines/gh/stardog-union/helm-charts)
 
 These charts install the Stardog Knowledge Graph platform on Kubernetes.
 

charts/stardog/Chart.lock

@@ -1,6 +1,6 @@
 dependencies:
 - name: zookeeper
   repository: https://raw.githubusercontent.com/bitnami/charts/eb5f9a9513d987b519f0ecd732e7031241c50328/bitnami
-  version: 5.5.1
-digest: sha256:eaac5e300a586dd12a580e20c6f97618da1cf825e93950ad5447d327b1275c4c
-generated: "2022-06-06T17:02:33.115306-07:00"
+  version: 8.1.2
+digest: sha256:90eb758ed622e7981f0972a4e695ab1ccb94a5da3ccc995a73c9135172edf252
+generated: "2023-04-27T10:55:36.971668-04:00"

charts/stardog/Chart.yaml

@@ -11,6 +11,6 @@ maintainers:
     url: https://www.stardog.com
 dependencies:
   - name: zookeeper
-    version: 5.5.1
+    version: 8.1.2
     repository: https://raw.githubusercontent.com/bitnami/charts/eb5f9a9513d987b519f0ecd732e7031241c50328/bitnami
     condition: zookeeper.enabled

charts/stardog/README.md

@@ -89,6 +89,35 @@ a separate location.
 - Shutdown all Stardog and ZooKeeper pods (e.g. using `helm delete`).
 - Install the new 2.x charts with the same version of Stardog you were running previously.
 
+### Upgrading Zookeeper
+
+Certain new versions of these charts will specify a newer version of ZooKeeper
+by default. This is because with new Stardog versions, support for new ZooKeeper
+versions is added and support for older ZooKeeper versions is removed. When 
+upgrading the ZooKeeper version, the steps are similar to the section above.
+
+- Stop all traffic and updates to your cluster or wait for them to end. You can 
+check for these using `stardog tx list`, `stardog-admin db status <db name>`,
+and `stardog-admin ps list`.
+- Backup Stardog home and copy the backup out of the k8s environment. The
+[Stardog documentation](https://www.stardog.com/docs/#_backing_up_and_restoring) includes
+an overview of the various options for backing up Stardog. Only S3 backups will copy
+data outside of the pods. If you use another backup method you will need to manually
+copy the data off the volume or snapshot the volumes to ensure the data is stored in
+a separate location.
+- Shutdown all Stardog and ZooKeeper pods without deleting the PVCs. This can be done by:
+    - Setting the `replicaCount` of the Stardog and ZooKeeper pods both to 0 then
+    running `helm upgrade` **OR**
+    - Running `helm delete`
+- Set the ZooKeeper image tag to a newer version in your `values.yaml` file
+- Bring the Stardog and Zookeeper pods back online. Using the previous examples, this would mean:
+    - Setting both `replicaCount` values back to their previous non-zero value 
+    then running `helm upgrade` **OR**
+    - Running `helm install`
+
+Failure to fully stop Stardog before upgrading ZooKeeper could result in putting
+the Stardog cluster in a non-functional state.
+
 Limitations
 -----------
 

charts/stardog/values.yaml

@@ -152,7 +152,7 @@ zookeeper:
       cpu: 1
   image:
     repository: bitnami/zookeeper
-    tag: 3.5.7
+    tag: 3.7.1-debian-11-r58
     pullPolicy: IfNotPresent
   logLevel: INFO
 #  livenessProbe: