CRItest for invalid registry and bad signature error codes

[SergeyKanzhelev]

What would you like to be added:

As a follow up from kubernetes/kubernetes#117717 it will be great to create cri tests to ensure that the proper error messages are returned from the CRI implementation as CRI takes weak dependency on those.

This may not work for every implementation, so need to validate it first and maybe have those tests as optional at first.

[saschagrunert]

Sounds like a good plan!

/help

[k8s-ci-robot]

@saschagrunert:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

Sounds like a good plan!

/help

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.

[sohankunkerkar]

/assign @sohankunkerkar

[sohankunkerkar]

@SergeyKanzhelev @saschagrunert, I believe we need to create two separate images in order to test the ErrRegistryUnavailable and ErrSignatureValidationFailed errors. I assume the placeholder for these two images would be located at gcr.io/k8s-staging-cri-tools/. However, I do not have access to create the images in that repository. Is it possible for someone to assist me in creating those two images there?

[saschagrunert]

ErrRegistryUnavailable can be tested by referring to a xyz.local registry where we ensure that it does not exist. Maybe by using a random hostname and double checking that no registry is running there.

The images in gcr.io/k8s-staging-cri-tools/ are not signed, so they may already qualify for a ErrSignatureValidationFailed test depending on how we configure the container runtime.