There is an issue with the way the Bookkeeper cluster is initialized. It is currently only initialized when running the minikube platform mode. This causes issues for any of the other platform modes. Also this causes an issue whenever the Init container runs again, because it wipes out any underlying data. This is an issue in Kubernetes clusters that may restart frequently. For example K3D and KinD clusters.
The proposed fix is to provide an initialize setting which will be defaulted to false, but can be explicitly set during installation of the Helm chart. This is how Pulsar Helm chart handles Bookkeeper initialization. Here is the Pulsar documentation that mentions the initialize setting: https://pulsar.apache.org/docs/en/helm-deploy/#deploy-pulsar-cluster-using-helm
There is an issue with the way the Bookkeeper cluster is initialized. It is currently only initialized when running the
minikube
platform mode. This causes issues for any of the other platform modes. Also this causes an issue whenever the Init container runs again, because it wipes out any underlying data. This is an issue in Kubernetes clusters that may restart frequently. For example K3D and KinD clusters.The proposed fix is to provide an
initialize
setting which will be defaulted to false, but can be explicitly set during installation of the Helm chart. This is how Pulsar Helm chart handles Bookkeeper initialization. Here is the Pulsar documentation that mentions theinitialize
setting: https://pulsar.apache.org/docs/en/helm-deploy/#deploy-pulsar-cluster-using-helm