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.
Alternative to vagrant · kubernetes-sigs/kubespray#12237 | Good First Issue