kubernetes-sigs/kubespray

Alternative to vagrant

Open

#12,237 创建于 2025年5月20日

在 GitHub 查看
 (9 评论) (0 反应) (0 负责人)HTML (10,380 star) (4,419 fork)batch import
help wantedkind/featurepriority/important-longtermtriage/accepted

描述

What would you like to be added

We have two remaining tests using it in CI which we will convert to kubevirt once the CI cluster has dual stack support.

But a simple local runner is useful for developpment.

Lima might be a possible alternative : https://github.com/lima-vm/lima/discussions/1749

Why is this needed

With the license change of vagrant, it's uncertain if Kubespray can still use it in the future. See https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md and https://kubernetes.slack.com/archives/C5P3FE08M/p1744649947234749 Some distributions have also started dropping it from their repo

贡献者指南

技术栈
dockershell
领域
devopsinfrastructureci cd
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
knowledge of Kubespray deploymentunderstanding of Vagrantbasic Linux administration
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate alternative local development tools to Vagrant for Kubespray, focusing on Lima as suggested. Review the linked Slack discussion and third party license policy. Evaluate feasibility of integrating Lima for local VM management. Check existing CI tests that use Vagrant and plan migration to kubevirt once dual stack support is available.