Migrate remaining containerd-build-* jobs to the community bucket and introduce postsubmit jobs

[upodroid]

Follow up to #29986
Part of kubernetes/k8s.io#1469
Part of #29722
Fixes #29995

I did a few changes:

• The build jobs now run as postsubmits. A build is triggered when a commit is merged on the relevant branches instead of building containerd every 30 minutes. (We can use that compute to test something more useful)
• The CI job runs once a day.
• I updated the OWNERS file in containerd folder to match the sig-node folder
• containerd jobs will be running on community infrastructure

[upodroid]

/cc @dims @tzneal

[dims]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, upodroid

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/containerd/containerd/OWNERS [dims]
• config/jobs/kubernetes/sig-node/OWNERS [dims]
• config/testgrids/kubernetes/containerd/OWNERS [dims]

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

[upodroid]

/retest

[upodroid]

/cc @SergeyKanzhelev

This is ready to be merged.

[bart0sh]

/assign @SergeyKanzhelev

[akhilerm]

Have a few comments on the changes:

Also 2 follow up changes need to be done:

1. The default bucket referred in containerd/containerd should also be changed.
2. References to cri-containerd-staging in the env files used for deploying VMs with containerd should be changed, else those node-e2e jobs will start failing.

[upodroid]

• The default bucket referred in containerd/containerd should also be changed.
• References to cri-containerd-staging in the env files used for deploying VMs with containerd should be changed, else those node-e2e jobs will start failing.

1. Not really required and might break other users
2. I will do this in a separate PR once this is merged. The old bucket will still be available but it will have stale containerd builds(by a few days which isn't critical).

Can I get a LGTM?

[akhilerm]

@upodroid I had one more question here #30025 (comment)

[upodroid]

As I said earlier, we can merge this PR now and I can open a separate one to adjust the containerd env files. I'll open it today for review. We'll have stale builds for containerd for a few hours/days after this is merged depending on how fast PRs are being merged in containerd.

[akhilerm]

/lgtm

[k8s-ci-robot]

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

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

In response to this:

Follow up to #29986
Part of kubernetes/k8s.io#1469
Part of #29722
Fixes #29995

I did a few changes:

• The build jobs now run as postsubmits. A build is triggered when a commit is merged on the relevant branches instead of building containerd every 30 minutes. (We can use that compute to test something more useful)
• The CI job runs once a day.
• I updated the OWNERS file in containerd folder to match the sig-node folder
• containerd jobs will be running on community infrastructure

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.

[mikebrow]

interesting