kubernetes-sigs/kubespray

Alternative to vagrant

Open

#12,237 opened on 2025年5月20日

GitHub で見る
 (9 comments) (0 reactions) (0 assignees)HTML (10,380 stars) (4,419 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.