Is there any way to expose a debug port in kafka connect pod?

[atrifyllis]

I am probably missing something fundamental, but how else do you remote debug kafka connect connectors? You need an exposed port in the host right?

For example, I can add this env variable in the pod's container but how do I expose port 5005 then?

  template:
    connectContainer:
      env:
        - name: JAVA_TOOL_OPTIONS
          value: -agentlib:jdwp=transport=dt_socket,address=*:5005,server=y,suspend=n

[scholzj]

No, there is no way to expose the port itself.

[atrifyllis]

So there is no way to remote debug kafka connect then?

[scholzj]

I don't think so.

[jakubmalek]

I think exposing a debug port poses too many security risks, and it's rather impractical solution for normal KC cluster. Bare in mind you need to connect to specific pod where your connector is deployed.
Normally you should enable it only in your local environment e.g. Minikube then you can easily forward the debug port with the kubectl and connect to the pod using the localhost address.

kubectl port-forward YOUR_CONNECT_POD 5005

In general you can edit the deployment manifest manually if you pause the reconciliation:
kubectl annotate kafkaconnect YOUR_KC_NAME strimzi.io/pause-reconciliation=true

With that you can add containerPort declaration and try to expose it with nodePort SVC, but I'm not sure if you can have selector to specific pod without use of statefulsets.

You can then restore the deployment back to normal by removing the annotation
kubectl annotate kafkaconnect kafka-connect strimzi.io/pause-reconciliation-

[atrifyllis]

This is what I ended up doing, thanks @jakubmalek . I don't know about security risks though, is thould at least be an opt-in option