Expose broker container port without listener

[z0rc]

I'm using Strimzi Operator to deploy AutoMQ Kafka variant and need to scrape metrics from it.

Unfortunately I cannot use metricsConfig spec, as AutoMQ doesn't have proper instrumentation for those jmx/strimzi exporters. Fortunately it has it's own instumentation, that can be enabled via configuration https://www.automq.com/docs/automq/observability/integrating-metrics-with-prometheus#solution-three:-pull-metrics-directly-from-the-server.

Problem is, I need to expose custom port in broker container spec to allow scraping of those metrics. AFAIU with strimzi the container port configuration is tightly coupled with listeners spec, but I don't think it's usable here.

Is there a way to expose custom broker container port with Strimzi? If not, I potentially can add a MutatingWebhook to patch in port in the Pod on creation, but need to make sure this won't confuse strimzi operator.

[scholzj]

No, that is not possible today without changing the code or without using a mutating webhook (which is probably easier in the long term than maintaining a fork of Strimzi). I think this should be pretty simple with the webhook and should not cause any issues to the operator (as long as you use your own port number of course). You might need to also add some network policies probably.

I guess you can also use the OLTP push metrics instead of pull metrics - which do not need a port to be exposed. But I guess you saw the in the docs you linked and for some reason do not want to use it.

[z0rc]

Thanks. I went ahead with mutating webhook using Kyverno. So far it's working okay, no conflicts with operator.

I guess you can also use the OLTP push metrics instead of pull metrics - which do not need a port to be exposed. But I guess you saw the in the docs you linked and for some reason do not want to use it.

This should work too. But in this case I use scraping via PodMonitor to maintain observability pattern for all services we have.