Add e2e tests to the images

[rmohr]

Basically do the following:

make cluster-up
RELEASE="$(curl http://storage.googleapis.com/kubevirt-prow/devel/release/kubevirt/kubevirt/stable.txt)"
kubectl apply -f https://github.com/kubevirt/kubevirt/releases/download/${RELEASE}/kubevirt-operator.yaml
kubectl apply -f https://github.com/kubevirt/kubevirt/releases/download/${RELEASE}/kubevirt-cr.yaml
kubectl -n kubevirt wait kv kubevirt --for condition=Available

Then pushing one image after the other:

docker build . -t blub
docker push blub

Then create a yaml with that image and wait until virtcl ssh can connect to the guest.

[ksimon1]

We can reuse automation which we already have in common-templates for golden images https://github.com/kubevirt/common-templates/blob/master/dvtemplates/build_k8s_cluster.sh
It builds, pushes image into cluster and tests it with templates

[kubevirt-bot]

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.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/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.

[rmohr]

/reopen

we still need to adjust CI

[kubevirt-bot]

@rmohr: Reopened this issue.

In response to this:

/reopen

we still need to adjust CI

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.

[rmohr]

/close

CI is now also in place with kubevirt/project-infra#2049 merged.

[kubevirt-bot]

@rmohr: Closing this issue.

In response to this:

/close

CI is now also in place with kubevirt/project-infra#2049 merged.

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.