+1 Thanks Fede
On Thu, Oct 8, 2026, 5:20 AM Luke Chen <[email protected]> wrote: > +1 for both the new base image and dropping Vagrant. > > Thank you, > Luke > > On Tue, Sep 15, 2026 at 2:42 AM Maroš Orsák <[email protected]> > wrote: > > > +1 for having a base image for STs deps. It would definitely make things > > easier. Same for dropping the Vagrant but let's see if there are more > > opinions. But I would definitely be interested in the details of how > > specifically you want to do it. > > > > Maros > > > > po 14. 9. 2026 o 2:42 Chia-Ping Tsai <[email protected]> napísal(a): > > > > > Hi all, > > > > > > I'd like to raise a discussion about our system test dependencies. I'm > > not > > > sure this needs a KIP, happy to write one if people think so. We keep > > > hitting the same issues in each release: > > > > > > 1. We forgot to upload files to the S3 mirror, and not every RM has > > > access to it. > > > 2. We forgot to update both the Dockerfile and vagrant file. > > > 3. The Dockerfile has 44 curl lines for the same thing, so each > > release > > > adds two more. > > > > > > Therefore, I'd like to propose a base image on GitHub Container > Registry > > > that contains only the released Kafka binaries. The benefits are: > > > > > > 1. It is built and pushed by a GitHub workflow that can be triggered > > > after each release, so no manual upload is needed. > > > 2. Only one file needs to be updated for each release. > > > 3. Both the Dockerfile and vagrant can pull everything from the base > > > image. > > > > > > Since the image is built once per release, we can fetch from ASF > download > > > links directly and drop the S3 mirror. > > > > > > Also, is anyone still using vagrant? If not, we could drop it. > > > > > > Any thoughts? > > > > > > Chia-Ping :) > > > > > >
