[
https://issues.apache.org/jira/browse/SOLR-16739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710178#comment-17710178
]
Houston Putman commented on SOLR-16739:
---------------------------------------
This would be shipped just like the s3-repository, or hadoop-auth, or auth of
the other modules, inside the solr tgz.
{quote}I hope this won't be shipped with Solr, but with the solr-operator,
right?
{quote}
The Solr Operator is completely separate and wouldn't make since to package
this code.
I just looked at what the current size of the module would be, and compared it
with the other existing modules:
{{268M .}}
{{40K ./scripting}}
{{160K ./ltr}}
{{352K ./jwt-auth}}
{{692K ./analytics}}
{{728K ./clustering}}
{{4.1M ./langid}}
{{11M ./opentelemetry}}
{{12M ./s3-repository}}
{{14M ./hadoop-auth}}
{{15M ./sql}}
{{29M ./analysis-extras}}
{{32M ./kubernetes}}
{{42M ./gcs-repository}}
{{48M ./hdfs}}
{{63M ./extraction}}
So it's up there in terms of size, but definitely not the largest. If we are
concerned about module size, it's probably best to ship a solr-slim.tgz (that
does not include any modules) and a solr.tgz (that includes all of the modules).
> 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]
