Added integration-prow-docker-containerd-linux-x86-64 prow test

[divysinghvi]

Added integration-prow-docker-containerd-linux-x86-64 prow test
issue : #21916

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

[ComradeProgrammer]

/ok-to-test

[minikube-bot]

Can one of the admins verify this patch?

[divysinghvi]

/retest

[divysinghvi]

/retest

[divysinghvi]

/retest

[divysinghvi]

/retest

[divysinghvi]

/reset

[medyagh]

if we are adding this to the kicbase this code wont be needed.

[divysinghvi]

yes we won't need if we are updating the kicbase image i did not knew how the kickbase image update worked

[medyagh]

if you want this change plz ask one of the maintainers to run
ok-to-build-image

[divysinghvi]

can you run ok-to-build-image sorry i am still confused about the process

[medyagh]

ok-to-build-image

[minikube-bot]

Hi @divysinghvi, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further.

[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-kvm-containerd-linux-x86-64	4cf3e56	link	true	/test integration-kvm-containerd-linux-x86-64
integration-docker-crio-linux-x86-64	4cf3e56	link	true	/test integration-docker-crio-linux-x86-64
integration-kvm-crio-linux-x86-64	4cf3e56	link	true	/test integration-kvm-crio-linux-x86-64
integration-kvm-docker-linux-x86-64	4cf3e56	link	true	/test integration-kvm-docker-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 21974 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 41.0s    │ 39.5s                  │
│ enable ingress │ 15.3s    │ 15.8s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 39.2s 40.9s 40.1s 40.4s 44.5s
Times for minikube (PR 21974) start: 39.5s 39.8s 39.3s 39.7s 39.0s

Times for minikube ingress: 15.8s 15.7s 15.2s 14.7s 15.2s
Times for minikube (PR 21974) ingress: 15.7s 15.7s 15.8s 15.7s 15.8s

docker driver with docker runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21974 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 22.3s    │ 21.8s                  │
│ enable ingress │ 11.0s    │ 10.6s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 22.8s 22.0s 21.1s 24.2s 21.5s
Times for minikube (PR 21974) start: 19.9s 24.5s 23.2s 20.9s 20.3s

Times for minikube ingress: 12.6s 10.6s 10.6s 10.6s 10.6s
Times for minikube (PR 21974) ingress: 10.6s 10.6s 10.6s 10.6s 10.6s

docker driver with containerd runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21974 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 21.7s    │ 19.8s                  │
│ enable ingress │ 20.3s    │ 20.5s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube start: 22.0s 21.7s 21.6s 22.7s 20.4s
Times for minikube (PR 21974) start: 19.4s 18.2s 19.2s 20.5s 21.8s

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

[minikube-pr-bot]

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

Environment	Test Name	Flake Rate
Docker_Windows (2 failed)	TestCertExpiration(gopogh)	Unknown
Docker_Windows (2 failed)	TestErrorSpam/setup(gopogh)	Unknown

Besides the following environments also have failed tests:

• Docker_Linux_crio: 37 failed (gopogh)

• KVM_Linux_crio: 2 failed (gopogh)

• Docker_Linux_crio_arm64: 40 failed (gopogh)

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