Ability to use CRI-O as runtime in kube-up (on Ubuntu for now)

[saschagrunert]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Analogous to containerd, we also need a job that uses CRI-O, both in
master and node. This PR enables us to install CRI-O automatically
when we use a ubuntu OS base image if it is not present on the image.
This also enables us to inject newer versions of containerd and runc to
help us test against them as well.

Which issue(s) this PR fixes:

Refers to #87931, kubernetes/test-infra#16589

Special notes for your reviewer:

cc @dims @aojea @mrunalp

Does this PR introduce a user-facing change?:

None

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

None

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: saschagrunert
To complete the pull request process, please assign wojtek-t
You can assign the PR to them by writing /assign @wojtek-t in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• cluster/gce/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[aojea]

does this mean we can have crio and containerd run at the same time?
may this cause a conflict or can both run at the same time?

[saschagrunert]

I think they can run in parallel, yes. Never actually tried it but running docker on CRI-O nodes should work too.

[haircommander]

@saschagrunert, @harche was also doing work in this space. maybe y'all can work together to get this through?

[harche]

Hi @saschagrunert, I have a WIP PR in test-infra for adding presubmit job for crio. Considering the recently merged support for cgroups v2, we are hoping to run those tests on Fedora 31+ node. @vpickard is helping me to identify a gcp proejct which can host Fedora 31 image (gcp doesn't have publicly available fedora images).

As of now there are no presubmit or periodic CRIO tests in test-infra.

[saschagrunert]

Hi @saschagrunert, I have a WIP PR in test-infra for adding presubmit job for crio. Considering the recently merged support for cgroups v2, we are hoping to run those tests on Fedora 31+ node. @vpickard is helping me to identify a gcp proejct which can host Fedora 31 image (gcp doesn't have publicly available fedora images).

As of now there are no presubmit or periodic CRIO tests in test-infra.

Alright is there anything I can do or should we close this one?

[harche]

@saschagrunert no need to close this one.

Maybe we can work together, on adding a crio presubmit job using ubuntu. I already have WIP PR for fedora based job, but we can collaborate and co-author that PR to have both Fedora and Ubuntu based presubmit jobs for CRIO if you wish.

Let me know what do you think.

[fejta-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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[saschagrunert]

/remove-lifecycle stale

[fejta-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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[k8s-ci-robot]

@saschagrunert: PR needs rebase.

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.

[saschagrunert]

Let's close this for now, I think we're moving into a different direction.