templates/*: make crun as the default container runtime

[sohankunkerkar]

- What I did
This commit sets crun as the default container runtime in OCP for 4.18

- How to verify it
I'm in the process of adding test coverage for this behavior.

- Description for the changelog
Make crun the default container runtime

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sohankunkerkar
Once this PR has been reviewed and has the lgtm label, please assign giuseppe for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• templates/master/01-master-container-runtime/OWNERS
• templates/worker/01-worker-container-runtime/OWNERS

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

[sohankunkerkar]

/payload 4.18 nightly blocking
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade-out-of-change
/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

[openshift-ci]

@sohankunkerkar: trigger 9 job(s) of type blocking for the nightly release of OCP 4.18

• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade
• periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.18-fips-payload-scan
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fc834420-7a78-11ef-92fd-410ffeb94bb8-0

trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade-out-of-change
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fc834420-7a78-11ef-92fd-410ffeb94bb8-1

[sohankunkerkar]

/payload-job periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance

[openshift-ci]

@sohankunkerkar: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/03af9ac0-7aa4-11ef-940d-6d187c9f16d0-0

[sohankunkerkar]

/retest

[sohankunkerkar]

/retest

[neisw]

/retest

[openshift-ci]

@sohankunkerkar: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-azure-ovn-upgrade-out-of-change	a19e325	link	false	/test e2e-azure-ovn-upgrade-out-of-change

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.