You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "dino2895 (Jira)" <ji...@apache.org> on 2026/10/11 13:45:00 UTC

[jira] [Assigned] (KAFKA-21260) Drop the Vagrant

     [ https://issues.apache.org/jira/browse/KAFKA-21260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dino2895 reassigned KAFKA-21260:
--------------------------------

    Assignee: dino2895  (was: Chia-Ping Tsai)

> Drop the Vagrant
> ----------------
>
>                 Key: KAFKA-21260
>                 URL: https://issues.apache.org/jira/browse/KAFKA-21260
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Chia-Ping Tsai
>            Assignee: dino2895
>            Priority: Minor
>              Labels: need-kip
>
> We used Vagrant to run system tests on virtual machines (local or EC2), but the Docker-based runner ({{{}tests/docker/run_tests.sh{}}}) is the better choice in this area, and it is the way most of us run the system tests today. The git history shows that we update the Vagrant code only when we make another Kafka release.
> In short, we should remove the {{{}Vagrantfile{}}}, {{{}vagrant/{}}}, {{{}vagrant-up.sh{}}}, and the related docs in {{tests/README.md}} to streamline our code base.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)