Added restart command after setting crio options

[kadern0]

Fixes #11729

Before:

After:

[k8s-ci-robot]

Hi @kadern0. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kadern0
To complete the pull request process, please assign ilya-zuyev after the PR has been reviewed.
You can assign the PR to them by writing /assign @ilya-zuyev 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:

• OWNERS

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

[minikube-bot]

Can one of the admins verify this patch?

[sharifelgamal]

/ok-to-test

[minikube-pr-bot]

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11968) |
+----------------+----------+---------------------+
| minikube start | 47.7s    | 47.3s               |
| enable ingress | 32.2s    | 31.7s               |
+----------------+----------+---------------------+

Times for minikube start: 49.6s 47.8s 47.6s 47.3s 46.4s
Times for minikube (PR 11968) start: 48.1s 46.1s 46.7s 48.5s 47.1s

Times for minikube ingress: 32.2s 32.4s 31.8s 31.3s 33.3s
Times for minikube (PR 11968) ingress: 31.7s 31.8s 32.2s 31.2s 31.3s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11968) |
+----------------+----------+---------------------+
| minikube start | 22.8s    | 21.7s               |
| enable ingress | 30.5s    | 27.1s               |
+----------------+----------+---------------------+

Times for minikube ingress: 29.5s 27.0s 34.5s 27.0s 34.5s
Times for minikube (PR 11968) ingress: 27.0s 28.0s 27.5s 26.6s 26.6s

Times for minikube start: 23.5s 22.3s 22.9s 22.8s 22.3s
Times for minikube (PR 11968) start: 21.5s 21.3s 21.9s 21.8s 21.7s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 11968) |
+----------------+----------+---------------------+
| minikube start | 40.6s    | 43.9s               |
| enable ingress |          |                     |
+----------------+----------+---------------------+

Times for minikube (PR 11968) start: 43.2s 43.7s 44.2s 44.1s 44.2s
Times for minikube start: 27.4s 44.3s 43.4s 44.0s 44.1s

[sharifelgamal]

@afbjorklund what do you think?

[afbjorklund]

I thought we already did a crio restart below, maybe it was removed since ?