Create containerd 1.5 canaries

[mmiranda96]

Create new canary jobs for containerd 1.5

Following the structure of canaries for v1.4, these are the new ProwJobs:

• ci-containerd-build-1-5-canary
• ci-containerd-node-e2e-1-5-canary
• ci-containerd-node-e2e-features-1-5-canary

Closes #23131

[k8s-ci-robot]

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

[mmiranda96]

/cc ehashman
/cc endocrimes
/cc dims

[ehashman]

/ok-to-test
/assign @endocrimes

[mmiranda96]

Gentle ping for another review.

[adisky]

also the kubekins images have been updated
from --> gcr.io/k8s-testimages/kubekins-e2e:v20210825-bb6d84a-master
to --> gcr.io/k8s-testimages/kubekins-e2e:v20210825-f1955d1-master

[mmiranda96]

/assign @spiffxp
PTAL

[spiffxp]

tl;dr I think these would better belong in kubernetes/sig-node/containerd.yaml, without the -canary suffixes

Apologies for the lack of documentation here, but generally jobs in sig-k8s-infra/canaries are duplicates of jobs elsewhere that run in the default cluster, solely to make sure they run OK in k8s-infra-prow-build. We probably have more jobs there than we need to at this point; they're intended to be temporary, long enough to verify whether a job that currently runs in default runs the same way in k8s-infra-prow-build

In this case, these jobs don't already exist in default, and they seem more directly under the purview of SIG Node.

[mmiranda96]

Moving now to the proper directory. Does it make sense to use the same base configuration as the jobs in the new directory? (changing base image, labels, arguments, and resources)

[spiffxp]

The only thing that comes to mind is the testgrids should also be something with the word sig-node in them, porbably sig-node-containerd.

As I'm looking at https://testgrid.k8s.io/sig-node-containerd I'm noticing the 1.4 e2e jobs appear to be failing, seems like the clusters aren't coming up? Might be good to figure out why those are failing (or drop them if no longer relevant)

[mmiranda96]

Apologies for the delay @spiffxp. I've moved the jobs to the proper directory. Additionally, I've filed #23915 to fix 1.4 canaries. I'll investigate on this before creating the new ones, I'm suspecting they will fail as well.
/hold

[spiffxp]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ehashman, mmiranda96, spiffxp

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:

• config/jobs/kubernetes/sig-node/OWNERS [ehashman,spiffxp]
• jobs/e2e_node/OWNERS [ehashman,spiffxp]

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

[mmiranda96]

Thanks to @adisky, 1.4 canaries are now passing. I feel more confident pushing this now.
/unblock

[mmiranda96]

/unhold

[k8s-ci-robot]

@mmiranda96: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key containerd.yaml using file config/jobs/kubernetes/sig-node/containerd.yaml

In response to this:

Create new canary jobs for containerd 1.5

Following the structure of canaries for v1.4, these are the new ProwJobs:

• ci-containerd-build-1-5-canary
• ci-containerd-node-e2e-1-5-canary
• ci-containerd-node-e2e-features-1-5-canary

Closes #23131

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.