Mancenter Clustered JMX
- Dominant language
- Mustache
- Stars
- 46
- Forks
- 87
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Hi -
It seems like the helm chart has no support for exposing a JMX port from management center
You can enable this-
```
.Values.mancenter.javaOpts
-Dhazelcast.mc.jmx.enabled=true
```
However as far as I can tell, there's no way to expand the template to expose the port used for JMX.
https://github.com/hazelcast/charts/blob/master/stable/hazelcast/templates/mancenter-statefulset.yaml#L84
This would be helpful to use the clustered JMX feature described here:
https://docs.hazelcast.com/management-center/5.3/integrate/jmx
With the standard hazelcast chart, you can use customPorts https://github.com/hazelcast/charts/blob/master/stable/hazelcast/templates/statefulset.yaml#L93
Thank you!
Contributor guide
Research direction
Start with stable/hazelcast/templates/mancenter-statefulset.yaml at the referenced port definition, then compare stable/hazelcast/templates/statefulset.yaml and its customPorts handling. Check how the chart values reach the templates; done means the Management Center JMX port can be configured and exposed through the Helm chart when clustered JMX is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100