apache / apache/solr-operator

Solr Cloud only allows 1 exposed port.

Open
#272 7 comments 0 reactions 0 assignees View on GitHub
custom kube options
Dominant language
Go
Stars
283
Forks
148
PR merge metrics
No merged PRs in 30d

Description

It would be helpful to be able to supply a list of ports in the solrAddressability instead of only have a single podPort possible. My specific use case is to be able to have both the normal port exposed to access to the solr cloud members but also the jmx port. My current workaround is to sidecar in a socat container to expose this port. I see no way to really have JMX function without having multiple exposed ports, and datadog monitoring uses JMX. I am happy to supply any more details necessary to understand this use case in full.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the solrAddressability and podPort configuration in the Solr Operator, then inspect how the Kubernetes exposure for Solr Cloud members is defined. Done means users can configure multiple exposed ports, including the normal Solr port and JMX, without needing a socat sidecar.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.