I think kafka-native is clearer. Over time, the graalvm images may be used for production too.
Ismael On Sat, Oct 28, 2023, 11:52 PM Manikumar <manikumar.re...@gmail.com> wrote: > Thanks for the explanation. I am fine with using ""kafka-local" as the > image name. > > On Fri, Oct 27, 2023 at 11:47 AM Krishna Agarwal < > krishna0608agar...@gmail.com> wrote: > > > Hi Manikumar, > > Thanks for the feedback. > > > > This image signifies 2 things: > > > > 1. Image should be used for the local development and testing purposes > > with fast startup times. (kafka-local) > > 2. To achieve (1) - we are providing a native executable for Apache > > Kafka in the docker image. (kafka-native) > > > > While "graalvm" is the underlying tool enabling this, I'm unsure if we > > should explicitly mention it in the name. > > I'd love to hear your thoughts on this. Do you prefer "kafka-native" > > instead of "kafka-local"? > > > > Regards, > > Krishna > > > > On Fri, Oct 20, 2023 at 3:32 PM Manikumar <manikumar.re...@gmail.com> > > wrote: > > > > > Hi, > > > > > > > For the native AK docker image, we are considering '*kafka-local*' as > > it > > > clearly signifies that this image is intended exclusively for local > > > > > > I am not sure, if there is any naming pattern for graalvm based images. > > Can > > > we include "graalvm" to the image name like "kafka-graalvm-native". > > > This will clearly indicate this is graalvm based image. > > > > > > > > > Thanks. Regards > > > > > > > > > > > > > > > On Wed, Oct 18, 2023 at 9:26 PM Krishna Agarwal < > > > krishna0608agar...@gmail.com> wrote: > > > > > > > Hi Federico, > > > > Thanks for the feedback and apologies for the delay. > > > > > > > > I've included a section in the KIP on the release process. I would > > > greatly > > > > appreciate your insights after reviewing it. > > > > > > > > Regards, > > > > Krishna > > > > > > > > On Fri, Sep 8, 2023 at 3:08 PM Federico Valeri <fedeval...@gmail.com > > > > > > wrote: > > > > > > > > > Hi Krishna, thanks for opening this discussion. > > > > > > > > > > I see you created two separate KIPs (974 and 975), but there are > some > > > > > common points (build system and test plan). > > > > > > > > > > Currently, the Docker image used for system tests is only supported > > in > > > > > that limited scope, so the maintenance burden is minimal. Providing > > > > > official Kafka images would be much more complicated. Have you > > > > > considered how the image rebuild process would work in case a high > > > > > severity CVE comes out for a non Kafka image dependency? In that > > case, > > > > > there will be no Kafka release. > > > > > > > > > > Br > > > > > Fede > > > > > > > > > > On Fri, Sep 8, 2023 at 9:17 AM Krishna Agarwal > > > > > <krishna0608agar...@gmail.com> wrote: > > > > > > > > > > > > Hi, > > > > > > I want to submit a KIP to deliver an experimental Apache Kafka > > docker > > > > > image. > > > > > > The proposed docker image can launch brokers with sub-second > > startup > > > > time > > > > > > and minimal memory footprint by leveraging a GraalVM based native > > > Kafka > > > > > > binary. > > > > > > > > > > > > KIP-974: Docker Image for GraalVM based Native Kafka Broker > > > > > > < > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-974%3A+Docker+Image+for+GraalVM+based+Native+Kafka+Broker > > > > > > > > > > > > > > > > > > Regards, > > > > > > Krishna > > > > > > > > > > > > > > >
