WIP: Fix KVM + CRI-O test failures: use cni0 bridge and skip preload test

[divysinghvi]

Fix KVM + CRI-O test failures: use cni0 bridge and skip preload test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: divysinghvi
Once this PR has been reviewed and has the lgtm label, please assign prezha for approval. For more information see the 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:

• OWNERS

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

[k8s-ci-robot]

Hi @divysinghvi. Thanks for your PR.

I'm waiting for a github.com 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-sigs/prow repository.

[minikube-bot]

Can one of the admins verify this patch?

[ComradeProgrammer]

/ok-to-test

[medyagh]

add link to documentation

[divysinghvi]

will do

[medyagh]

seems like we are changing this for everyeone all runtimes ? can you add more contexts maybe Before/AFter this PR
and also maybe this could be Two Prs for two different test cases?

[divysinghvi]

I was experimenting with something it did not work will remove this

[k8s-ci-robot]

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

Test name	Commit	Details	Required	Rerun command
integration-docker-crio-linux-x86-64	83cf6fd	link	true	/test integration-docker-crio-linux-x86-64
integration-kvm-docker-linux-x86-64	83cf6fd	link	true	/test integration-kvm-docker-linux-x86-64
integration-kvm-crio-linux-x86-64	83cf6fd	link	true	/test integration-kvm-crio-linux-x86-64

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[minikube-pr-bot]

kvm2 driver with docker runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 22054 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 42.6s    │ 43.4s                  │
│ enable ingress │ 16.2s    │ 15.9s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 43.7s 42.8s 41.0s 43.0s 42.6s
Times for minikube (PR 22054) start: 40.5s 44.1s 45.1s 44.1s 43.1s

Times for minikube ingress: 16.8s 15.8s 16.3s 15.8s 16.3s
Times for minikube (PR 22054) ingress: 15.8s 16.3s 15.8s 15.8s 15.8s

docker driver with docker runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 22054 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 22.6s    │ 23.2s                  │
│ enable ingress │ 16.7s    │ 10.8s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube ingress: 10.6s 41.1s 10.6s 10.6s 10.6s
Times for minikube (PR 22054) ingress: 10.6s 11.6s 10.6s 10.6s 10.6s

Times for minikube start: 23.0s 23.0s 21.9s 20.5s 24.4s
Times for minikube (PR 22054) start: 24.0s 20.7s 23.3s 23.9s 24.3s

docker driver with containerd runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 22054 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 20.4s    │ 20.8s                  │
│ enable ingress │ 20.5s    │ 20.5s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube ingress: 20.1s 20.1s 21.1s 20.1s 21.1s
Times for minikube (PR 22054) ingress: 21.1s 20.1s 20.1s 21.1s 20.1s

Times for minikube start: 17.9s 21.5s 19.4s 20.5s 22.6s
Times for minikube (PR 22054) start: 19.9s 21.8s 22.0s 20.5s 19.9s

[minikube-pr-bot]

Here are the number of top 10 failed tests in each environments with lowest flake rate.

Environment	Test Name	Flake Rate

Besides the following environments also have failed tests:

• KVM_Linux_crio: 1 failed (gopogh)

• Docker_Linux: 11 failed (gopogh)

• Docker_Linux_crio: 29 failed (gopogh)

• Docker_Linux_containerd_arm64: 34 failed (gopogh)

• Docker_Linux_containerd: 23 failed (gopogh)

• none_Linux: 14 failed (gopogh)

• Docker_Linux_crio_arm64: 55 failed (gopogh)

To see the flake rates of all tests by environment, click here.