Fix Kafka Connect healthcheck (#11 #12)#1
Conversation
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR updates the Kafka Connect configuration to fix healthcheck issues by removing the incorrect SASL_PLAINTEXT:// prefix from the bootstrap servers configuration and properly separating the security protocol setting.
However, there is one critical issue that must be addressed: the CONNECT_REST_ADVERTISED_HOST_NAME is set to localhost, which will break inter-container communication. This needs to be changed to connect to match the service name used in Docker networking (line 124 references http://connect:8083/connectors).
After fixing this issue, the PR should be ready to merge.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
| CONNECT_INTERNAL_KEY_CONVERTER: org.apache.kafka.connect.storage.StringConverter | ||
| CONNECT_INTERNAL_VALUE_CONVERTER: org.apache.kafka.connect.storage.StringConverter | ||
| CONNECT_REST_ADVERTISED_HOST_NAME: kafka | ||
| CONNECT_REST_ADVERTISED_HOST_NAME: localhost |
There was a problem hiding this comment.
🛑 Configuration Error: Setting CONNECT_REST_ADVERTISED_HOST_NAME to localhost will prevent other services from reaching Kafka Connect's REST API. The script at line 124 uses which relies on Docker's service discovery. Setting the advertised hostname tolocalhostcauses Kafka Connect to advertise itself as reachable atlocalhost, but other containers cannot reach it at that address—they need the service name connect`.
| CONNECT_REST_ADVERTISED_HOST_NAME: localhost | |
| CONNECT_REST_ADVERTISED_HOST_NAME: connect |
1 participant
Stacked on PR lf-edge#9