[
https://issues.apache.org/jira/browse/SOLR-16739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710138#comment-17710138
]
Houston Putman commented on SOLR-16739:
---------------------------------------
This wouldn't go in solr core, it would go into a new Solr module for
kubernetes integration. (to be clear, under the solr/modules/kubernetes
directory)
bq. I think as part of this effort, we should build pluggable interfaces by
which a separate package/plugin/jar can be used to provide a kubernetes impl,
but spare others who don't need this
That's exactly the point here. If you look at the first sub-issue, its creating
a new subclass of the ConfigSetService, which is a pluggable interface.
And if there are new pluggable interfaces that need to be created (such as
custom loading of the security.json), that would be a part of this work as well.
> Introduce Solr Kubernetes Module
> --------------------------------
>
> Key: SOLR-16739
> URL: https://issues.apache.org/jira/browse/SOLR-16739
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: module - kubernetes
> Reporter: Houston Putman
> Priority: Major
>
> As described in
> [SIP-18|https://cwiki.apache.org/confluence/display/SOLR/SIP-18%3A+A+Solr+Kubernetes+Module+for+native+integration],
> a Kubernetes module for Solr would help users run much more natively, when
> used with the Solr Operator.
> This is an umbrella issue and each functionality of the Kubernetes Module
> will be handled in child issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
