Discuss: Adding a KubeVirt Management Platform

[rmohr]

A few people from KubeVirt would be happy to explore adding a kubevirt platform to hypershift. I would be happy to get some feedback if that is welcome.

If so, here the steps I could identify which would probably need to be addressed:

hypershift binary

• Move aws create behind hypershift create cluster aws and hypershift destroy cluster aws (Minimal commandline implementation for "None" platforms #630)
• Add a kubevirt provider: hypershift create cluster kubevirt (Kubevirt platform #779)

controller binaries

• Refactor aws capi provision to make capi available for other platforms (Create platform interface for HostedCluster controller. #719)
• Add the KubeVirt platform using this capi provider: https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt (Kubevirt platform #779)

testing

• Test the KubeVirt platform with openshift virtualization (openshifts included kubevirt) in openshift-ci
• Test the KubeVirt platform in kubevirt-ci?

[aelbarkani]

If this is achieved, OpenShift would be a 100% hyperconverged infrastructure. So clearly +1 !
I'm seeing here though a decision to drop support for KubeVirt in OpenShift installer. Also this repo doesn't seem to be maintained, so hopefully we can have more insights from Redhat team on the roadmap about KubeVirt support :).

[fabiand]

We want to build the right approach to bring up tenant clusters. And the two links you have provided above illustrate a previous exploration.

[aelbarkani]

Hi @fabiand ! Thanks for your answer. If you have more information about why KubeVirt wasn't a good idea for this purpose I'm interested !

[rmohr]

A first WIP PR by @nirarg finally exists: #779

[rmohr]

#779 just merged. We still have to secure our progress with CI and testing and work on official capik providers, ... but basic functionality exists.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.