[
https://issues.apache.org/jira/browse/KAFKA-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068519#comment-17068519
]
Jordan Moore commented on KAFKA-9774:
-------------------------------------
Happy to take this on. And already working on a POC here (ignore the README and
the project name, I started working on only the pom and the main class in this
branch) -
[https://github.com/cricket007/kafka-streams-jib-example/tree/feature/connect-distributed]
> Create official Docker image for Kafka Connect
> ----------------------------------------------
>
> Key: KAFKA-9774
> URL: https://issues.apache.org/jira/browse/KAFKA-9774
> Project: Kafka
> Issue Type: Task
> Components: build, KafkaConnect, packaging
> Affects Versions: 2.4.1
> Reporter: Jordan Moore
> Priority: Major
> Labels: build, features
> Attachments: image-2020-03-27-05-04-46-792.png,
> image-2020-03-27-05-05-59-024.png
>
>
> This is a ticket for creating an *official* apache/kafka-connect Docker
> image.
> Does this need a KIP? - I don't think so. This would be a new feature, not
> any API change.
> Why is this needed?
> # Kafka Connect is stateless. I believe this is why a Kafka image is not
> created?
> # It scales much more easily with Docker and orchestrators. It operates much
> like any other serverless / "microservice" web application
> # People struggle with deploying it because it is packaged _with Kafka_ ,
> which leads some to believe it needs to _*run* with Kafka_ on the same
> machine.
> I think there is separate ticket for creating an official Docker image for
> Kafka but clearly none exist. I reached out to Confluent about this, but
> heard nothing yet.
> !image-2020-03-27-05-05-59-024.png|width=740,height=196!
>
> Zookeeper already has one , btw
> !image-2020-03-27-05-04-46-792.png|width=739,height=288!
> *References*:
> [Docs for Official
> Images|[https://docs.docker.com/docker-hub/official_images/]]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
