cp-docker-images | Docker images for Confluent Platform | Continuous Deployment library

I am deploying Kafka-connect on Google Kubernetes Engine (GKE) using cp-kafka-connect Helm chart in distributed mode.

A working Kafka cluster with broker and zookeeper is already running on the same GKE cluster. I understand I can create connectors by sending post requests to http://localhost:8083/connectors endpoint once it is available. However, Kafka-connect container goes into RUNNING state and then starts loading the jar files and till all the jar files are loaded the endpoint mentioned above is unreachable.

I am looking for a way to automate the step of manually exec the pod, check if the endpoint is ready and then send the post requests. I have a shell script that has a bunch of curl -X POST requests to this endpoint to create the connectors and also have config files for these connectors which work fine with standalone mode (using Confluent platform show in this confluent blog).

Now there are only two ways to create the connector:

1. Somehow identify when the container is actually ready (when the endpoint has started listening) and then run the shell script containing the curl requests
2. OR use the configuration files as we do in standalone mode (Example: $ /confluent local load connector_name -- -d /connector-config.json)

Which of the above approach is better?

Is the second approach (config files) even doable with distributed mode?

• If YES: How to do that?
• If NO: How to successfully do what is explained in the first approach?

EDIT: With reference to his github issue(thanks to @cricket_007's answer below) I added the following as the container command and connectors got created after the endpoint gets ready: