/hold

I'll cancel it once the bucket is populated

/approve
/lgtm

There is a snag. Some of the env files are used by containerd/containerd node-e2e presubmits and fixing those jobs to use kubetest2 + migrate to community cluster is hard. Details are at #30159

I can allow the [email protected] service account to write to the community bucket and merge it on Monday.

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

While doing gsutil ls gs://k8s-staging-cri-tools/containerd, do you happen to know what are the first 5 entries. Are they related to the PR runs? A bit confused that same item has entry inside the main directory and also in commit hash directory.

gs://k8s-staging-cri-tools/containerd/25d05956080b50b5bdf77d69da4820ee445d8a8b/
gs://k8s-staging-cri-tools/containerd/47be539f2cbc6aebb1a55b9365aaf093e03fb604/
gs://k8s-staging-cri-tools/containerd/5d4c71af23ccb035bf9d59f9badb87776fc7880f/
gs://k8s-staging-cri-tools/containerd/722f8def5a46aa1794c19966cbc3bf0220ef3c26/
gs://k8s-staging-cri-tools/containerd/9e16b5a80a5e37bf8989d3d69c47a07016d61f70/
gs://k8s-staging-cri-tools/containerd/main/
gs://k8s-staging-cri-tools/containerd/release-1.6/
gs://k8s-staging-cri-tools/containerd/release-1.7/

Those are PRs that were built and used in a containerd/containerd e2e test.

As soon as containerd/containerd#8862 is merged, I'll cancel the hold from this build.

We are currently testing 5 commits behind for jobs that test against containerd's HEAD.
https://testgrid.k8s.io/containerd-postsubmits#post-containerd-build

https://github.com/containerd/containerd/compare/6eb90a6..59959b3

/hold cancel

There is a circular dependancy. The change in containerd doesn't work because the env file still has the old bucket. I'll merge this PR which should allow the e2e tests in containerd/containerd to pass. Merging that PR and cherrypicking the fixes to 1.6 and 1.7 should resolve all the flakes that will be triggered.