Closed agradouski closed 2 years ago
This is related to this issue #84
@isaacdorfman can you also please start investigating kubernetes-sigs/image-builder
project and see if that's something we can use to generate disk images that work for capk
One comment: for CNI, we should leave it to user to choose just like other cloud provider doing for cluster api, end-user may not want or like built-in CNI provided us.
Here some of my experience on image-builder
, FYI.
I built a preliminary image based on kubernetes-sigs/image-builder
for openstack cluster api months ago, it does generate qcow2 image and it should work for kubevirt because both are based on KVM underneath, I gave a try on kubevirt cluster api, seems it working, not well intensively tested but at least workload kubernetes cluster is up, however some parameter may need to tune for kubevirt cluster api user case.
awesome, thanks for sharing @wangxin311
/assign @isaacdorfman
Isaac is working on this here, https://github.com/kubernetes-sigs/image-builder/pull/847
@davidvossel: GitHub didn't allow me to assign the following users: isaacdorfman.
Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
From CAPK community meeting discussion on Feb 1 (https://docs.google.com/document/d/1ZAnRLCKOVbDqrsrYis2OR0aZIAlqp576gCJVCkMNiHM), we need to find (or build and publish) a cluster node image, in order to truly unlock CAPK for developers. Also, it is a blocker for CAPK quick start guide.
Discussion points:
kubevirtci
fedora image for testing: https://github.com/kubevirt/kubevirtci/blob/main/cluster-provision/images/vm-image-builder/fedora-kubeadm/cloud-configkubeadm
installedkubernetes-sigs/image-builder
project can save us some effort