Closed moshloop closed 4 years ago
please outline the details on how this framework will be implemented.
/milestone Next /priority awaiting-more-evidence
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
This will be covered, at least at a cluster-api level by the testing CAEP (as of this comment this document is still early and hasn't been edited yet) https://docs.google.com/document/d/1SZkKoDok62eWHg5UVOmc96gW8KET69uNHZ4nWV0yyBs/edit
/remove-lifecycle stale /milestone Next /priority important-longterm
/remove-priority awaiting-more-evidence
closing this in favor of the CAEP proposal https://github.com/kubernetes-sigs/cluster-api/pull/1571
/close
@chuckha: Closing this issue.
If we are generating cloud-init then a KVM/QEMU based framework should work - AppVeyor supports nested virtualization for CI, and we could potentially work with test-infra to get some nested virtualization capable runners on GCP.
1) Generate cloud-init for controller 2) Spin up a KVM instance with cloud-int and wait for ip 3) Generate cloud-init for worker 4) Spin up second KVM instance 5) Test that both nodes have registered/joined.