search

strimzi / strimzi-kafka-operator

Apache Kafka® running on Kubernetes
https://strimzi.io/
Apache License 2.0
4.84k stars 1.3k forks source link

[Bug]: cannot add an additional variable for JMX to the broker #9280

Closed bth8939 closed 11 months ago

bth8939 commented 1 year ago

Bug Description

Hello,

I would like to know how to expose the broker JMX outside the kubernetes cluster by deleting the jmxremote.ssl (exposure works but with ssl).

the goal is to be able to supervise metrics with zabbix

In short, I would like to have these parameters at the broker boot:

-Dcom.sun.management.jmxremote.port=9999 \ -Dcom.sun.management.jmxremote.rmi.port=9999 \ -Dcom.sun.management.jmxremote.local.only=false \ -Dcom.sun.management.jmxremote.authenticate=false \ -Dcom.sun.management.jmxremote.ssl=false

This is my configuration:

`template: kafkaContainer: env:

Thank for your help.

`

Steps to reproduce

No response

Expected behavior

No response

Strimzi version

strimzi-kafka-operator-0.1.0

Kubernetes version

v1.24.16-eks-2d98532

Installation method

helm

Infrastructure

Amazon EKS

Configuration files and logs

No response

Additional context

No response

scholzj commented 1 year ago

I assume the Strimzi 0.1.0 is just some typo?

We support exposing of JMX using the jmxOptions field. We do not support any other way of exposing JMX or any advanced configurations. That said, we do not use SSL for JMX, so you should not need to change anything with regard to that.

ppatierno commented 1 year ago

Discussed on the Community call on 02.11.2023: @k-wall is going to take a look at this because something that he already faced in the past.

scholzj commented 1 year ago

What is there to look into? I do not think there is enough information here to work on this and more details need to be provided by the user.

k-wall commented 1 year ago

Sorry, the comment recorded yesterday during triage gave the wrong impression of my intent.

It was some of the words in the issue resonated with me. I thought I might have had some additional information to share, over what @scholzj had said already. It turns out, I don't have anything more to add beyond jmxOptions already suggested.

I agree there is nothing more that can be done unless further clarification from the user.

scholzj commented 11 months ago

Discussed on the community call on 30.11.2023: As discussed in the previous comments, to expose JMX, you should use the jmxOptions field and not configure the environment variables directly.