configure the crictl yaml file to avoid the warning

[jiefenghe]

fixes #10175

Kubernetes doesn't require crictl for docker, until the cri-dockerd is in use.
Adding the /etc/crictl.yaml to avoid the crictl warning.
Tested locally.

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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

[k8s-ci-robot]

Welcome @jiefenghe!

It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/minikube has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @jiefenghe. 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.

[minikube-bot]

Can one of the admins verify this patch?

[jiefenghe]

I signed it.

Added a ticket to the CLA issue: https://jira.linuxfoundation.org/plugins/servlet/theme/portal/4/SUPPORT-3834

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afbjorklund, jiefenghe

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [afbjorklund]

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

[medyagh]

/ok-to-test

[medyagh]

thank you very much for fixing this @jiefenghe would u plz sign the CLA so we can accept this contribution ?
https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/

[jiefenghe]

/check-cla

[jiefenghe]

I signed it.

[jiefenghe]

thank you very much for fixing this @jiefenghe would u plz sign the CLA so we can accept this contribution ?
https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/

Sorry It's a mess now. I have signed the CLA. But my initial commit was linked to the wrong email. So I did git commit --amend --reset-author to update the email. And tried to push to my local branch. But looks like the issue is still not resolved.

[medyagh]

thank you very much for fixing this @jiefenghe would u plz sign the CLA so we can accept this contribution ?
https://help.github.com/articles/why-are-my-commits-linked-to-the-wrong-user/

Sorry It's a mess now. I have signed the CLA. But my initial commit was linked to the wrong email. So I did git commit --amend --reset-author to update the email. And tried to push to my local branch. But looks like the issue is still not resolved.

feel free to reopen a new PR with right commit author.

[priyawadhwa]

Hey @jiefenghe thanks for fixing this!

We have a temporary fix which parses out the STDERR warning for one of our tests, could you also remove this code, and the comment above it, now that is is unnecessary?

minikube/test/integration/start_stop_delete_test.go

Lines 293 to 294 in 7de5bf7

	index := strings.Index(stdout, "{")
	stdout = stdout[index:]

Thank you!

[jiefenghe]

Hey @jiefenghe thanks for fixing this!

We have a temporary fix which parses out the STDERR warning for one of our tests, could you also remove this code, and the comment above it, now that is is unnecessary?

minikube/test/integration/start_stop_delete_test.go

Lines 293 to 294 in 7de5bf7

	index := strings.Index(stdout, "{")
	stdout = stdout[index:]

Thank you!

Opened a new PR with the update #10221