Support uploading configsets through the operator about solr-operator HOT 2 OPEN

Currently the only alternatives are to either build the image with the configsets or to upload one through the API before creating the configsets.

@whitleykeith Did you mean "or to upload one through the API before creating the collections" (and not configsets)?

If so, I'm wondering how to upload the configset between the creation of the kind: SolrCloud object, and the kind: SolrCollection object. Could you please give me more details about this?

from solr-operator.

First question is - should it be a configSet bootstrapping feature that will only be run on first startup if a configset with that name does not already exist...

OR - should it be a mechanism to manage configset updates through the operator?

As a bootstrapping feature we just need an initContainer which looks for a CM and uploads it with a CLI command.

But as a management feature it would more look like a SolrConfigSet CRD, where you could create, update, delete. For this to make sense, Solr should supported making a configSet Read-Only, so it is "owned" by the operator, since changes from ConfigSet API would be overwritten on next CM change...

from solr-operator.