Hey Joel, 1. You are correct, only solr.xml and log4j2.xml are currently supported. 2. Are you looking at the "SolrCloud.spec.customSolrKubeOptions.podOptions.volumes" section? If so, then yes, this is a way to mount whatever extra volumes you want to add to your Solr container, including a configMap if you so desire. However, that doesn't mean that Solr will do anything with the data you have loaded into the container. It will sit there and wait for you to do something with it. In case of the new option of loading configSets from disk, this might be useful for that whenever the Solr feature is merged and released. This option has nothing to do with Solr, but is just a way for you to customize your pod, i.e. adding extra volumes.
The broad answer here is that the Solr Operator doesn't want to be in the business of managing internal Solr resources like a Config Set. We have already removed Collection and Alias support from the operator because it wasn't a good fit for the project. (I can expand on this if you would like) Our stance currently is to encourage users to use the ConfigSet API <https://solr.apache.org/guide/8_9/configsets-api.html> for any configSet management they want to do, much like we encourage users to use the Collections API for managing Collections & Aliases. - Houston On Thu, Jul 15, 2021 at 9:58 AM Joel Bernstein <[email protected]> wrote: > I've been digging into the ConfigMap support in the Solr operator. Based on > the documentation only the solr.xml and log4j2.xml seem to be supported by > the Solr operator. A couple questions about this: > > 1) Am I correct in my reading of the documentation or is there broader > support for config files? > > 2) I also see this in the SolrCloud CRD: > > > *"If unspecified, each key-value pair in the Data field of the referenced > ConfigMap will be projected into the volume as a file whose name is the key > and content is the value. If specified, the listed keys will be projected > into the specified paths, and unlisted keys will not be present. If a key > is specified which is not present in the ConfigMap, the volume setup will > error unless it is marked optional. Paths must be relative and may not > contain the '..' path or start with '..'."* > > This seems to imply broader support, but the ConfigMap docs reference a > different part of the CRD under "configMapOptions". > > Thanks! > > Joel Bernstein > http://joelsolr.blogspot.com/ >
