HoustonPutman commented on issue #399: URL: https://github.com/apache/solr-operator/issues/399#issuecomment-1027060321
So there is no issue with the helm charts, or the Solr Operator really. The Solr Operator utilizes many of the Kubernetes built-in-resources to run Solr, included the `StatefulSet`. The operator relies on Kubernetes to manage the PVCs mostly itself through the StatefulSet controller. As a part of defining a StatefulSet, you can provide a PVC template that it will use to create a PVC for every pod in the statefulSet. Since your PVCs are not able to be dynamically provisioned, you will need to create your PVs for them to map to before creating your SolrCloud (as you mentioned). You need to make sure that you are creating at least the same number of PVs as the number of SolrCloud pods you have requested. As to why it can't bind the PVC to your PV, have you made sure that you are setting the same StorageClass for your PV and PVCs (the same one you are creating your PVs with)? The PVCs and PVs cannot bind if they do not have the same storageClassName and meet the size requirements in your PVC. (You can find all of the PVC options for you Solr pods here: https://artifacthub.io/packages/helm/apache-solr/solr#data-storage-options) Looking through the single PV that you are creating, it is not setting a storage class, while your SolrCloud PVC spec is setting a storage class of "gp2" (as shown in your `kubectl describe pvc` above). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
