Thanks Krishna. I will go ahead and vote.
Justine
On Fri, Feb 2, 2024 at 1:30 AM Krishna Agarwal
wrote:
> Hi Justine,
> Thanks for the feedback.
>
> I have added the above comparison results to the KIP.
>
> Given the widespread use of Alpine, the likelihood of encountering issues
> is minimal.
Hi Justine,
Thanks for the feedback.
I have added the above comparison results to the KIP.
Given the widespread use of Alpine, the likelihood of encountering issues
is minimal. Ubuntu, being a more comprehensive image, is expected to be
lesser prone to such challenges.
Considering that we are ini
Hey Krishna,
Can we include the perf results between the distroless/alpine/ubuntu images
in the KIP?
I also noticed
- Alpine employs the apk package manager, which, being relatively less
popular, may pose challenges in the future. There's a potential risk that
certain libraries we might
Hi Ismael,
Would you happen to have any remaining concerns regarding the selection of
the base Docker image?
Alternatively, do you have any additional suggestions or insights?
Regards,
Krishna
On Fri, Nov 24, 2023 at 1:16 AM Krishna Agarwal <
krishna0608agar...@gmail.com> wrote:
> Hi Ismael,
>
Hi Ismael,
In my pursuit of a lightweight base image, I initially considered Alpine
and Distroless
1. The next best option I explored is the Ubuntu Docker image(
https://hub.docker.com/_/ubuntu/tags) which is a more complete image.
It has a size of 70MB compared to the 15MB of the Alpine
Hi Krishna,
I am still finding it difficult to evaluate this choice. A couple of things
would help:
1. How much smaller is the alpine image compared to the best alternative?
2. Is there any performance impact of going with Alpine?
Ismael
On Wed, Nov 22, 2023, 8:42 AM Krishna Agarwal
wrote:
>
Hi Ismael,
Thanks for the feedback.
The alpine image does present a few drawbacks, such as the use of musl libc
instead of glibc, the absence of bash, and reliance on the less popular
package manager "apk". Considering the advantage of a smaller image size
and installing the missing packages(glibc
Hi,
One question I have is regarding the choice to use alpine - it would be
good to clarify if there are downsides (the upside was explained - images
are smaller).
Ismael
On Fri, Sep 8, 2023, 12:17 AM Krishna Agarwal
wrote:
> Hi,
> I want to submit a KIP to deliver an experimental Apache Kafka
Hi Justine,
Thanks for the feedback.
1. I have added the name of the other image in the KIP.
2. By experimental we mean the docker image is intended for local
development and testing usage.
GraalVM Native-Image tool is still in maturing stage, hence the usage of
this image for produ
Hey -- just catching up here, since I saw the vote thread. I had 2
questions that I'm not sure got answered from the previous discussion.
1. Can we update the KIP to include the name of the other image so if
someone stumbles across this KIP they know the name of the other one?
2. Did we cover what
Hi,
Thanks for the insightful feedback on this KIP.
As there are no ongoing discussions, I'm considering moving into the voting
process.
Your continued input is greatly appreciated!
Regards,
Krishna
On Fri, Sep 8, 2023 at 12:47 PM Krishna Agarwal <
krishna0608agar...@gmail.com> wrote:
> Hi,
> I
Hi Krishna, thanks for the updates, LGTM.
On Mon, Oct 30, 2023 at 3:36 PM Krishna Agarwal
wrote:
>
> Hi Federico,
> Thanks for the feedback.
>
>1. Yes, we will add the building, testing and scanning automation for
>this Docker Image along with the flow mentioned in KIP-975. (Updated in th
Hi Federico,
Thanks for the feedback.
1. Yes, we will add the building, testing and scanning automation for
this Docker Image along with the flow mentioned in KIP-975. (Updated in the
KIP)
2. Added the other alternatives to the "rejected alternatives" section,
instead of the main se
Thanks for the feedback.
I have updated the KIP with "kafka-native" as the accepted docker image
name.
Regards,
Krishna
On Sun, Oct 29, 2023 at 10:42 PM Ismael Juma wrote:
> I think kafka-native is clearer. Over time, the graalvm images may be used
> for production too.
>
> Ismael
>
> On Sat,
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 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 <
> k
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 dev
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-nat
Hi Krishna, thanks for updating the KIP and all the work you are
putting into that.
The release process LGTM. In the other KIP I see that there will be
some automation for building, testing and scanning for CVEs. Is this
also true for native images?
I see you are proposing to use Alpine as the ba
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 w
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 wrote:
> Hi Krishna, thanks for opening this
Hi Ismael,
Thanks for the feedback.
I noticed that the graalvm-reachability-metadata project now includes
> kafka-clients[1]. Worth checking if the metadata over there matches what
> we've observed for our own attempt.
>
After reviewing the graalvm-reachability-metadata, I observed that they
have
Hi Krishna,
Thanks for the KIP. The results are impressive! A few quick comments:
1. I noticed that the graalvm-reachability-metadata project now includes
kafka-clients[1]. Worth checking if the metadata over there matches what
we've observed for our own attempt.
2. Can we please add peak memory
Hi Federico,
I suggest taking this conversation to KIP-975 and keeping this one to the
graalvm specifics.
Ismael
On Fri, Sep 8, 2023 at 2:38 AM Federico Valeri wrote:
> Hi Krishna, thanks for opening this discussion.
>
> I see you created two separate KIPs (974 and 975), but there are some
> c
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. Provid
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
25 matches
Mail list logo