Remove issue comment on pull-kubernetes-node-e2e-containerd

[hasheddan]

This job was previously disabled in #18356 due to consistent timeout, which has
now been addressed by moving it to a new GCP project in #18409.

Signed-off-by: hasheddan georgedanielmangum@gmail.com

/cc @dims @liggitt

[dims]

/approve
/assign @spiffxp @BenTheElder

[hasheddan]

@spiffxp @BenTheElder could one of you give a lgtm if this looks okay?

[BenTheElder]

cc @liggitt

we've been working to minimize the number of default presubmit jobs (as opposed to postsubmit, periodic) which are especially resource heavy (run on every pushed commit) and increase the odds of a flake blocking merges

[BenTheElder]

I'm not sure what the cost/benefit is on this job specifically, or if we'd also wind up with yet another one for cri-o.

see also discussion in kubernetes/kubernetes#92937

[liggitt]

starting with this in a periodic job with good alerting, and a run_always: false PR job that can be manually triggered when desired would be my recommendation

if we see the periodic job getting broken frequently due to merged changes the other node e2e doesn't catch we can consider ways to prevent that

[hasheddan]

@liggitt sounds good, will update

[hasheddan]

@dims should this still have name pull-kubernetes-node-e2e-containerd as a periodic job?

[dims]

@hasheddan we have a periodic CI job already if i remember right

[hasheddan]

@dims there are a few e2e containerd node tests it looks like. If those are sufficient is any action needed here? I guess we could just drop the comment about re-enabling for now

[dims]

@hasheddan +1

[hasheddan]

@dims okay I think this is ready now :)

[dims]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [dims]

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

[k8s-ci-robot]

@hasheddan: Updated the job-config configmap in namespace default at cluster default using the following files:

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

In response to this:

This job was previously disabled in #18356 due to consistent timeout, which has
now been addressed by moving it to a new GCP project in #18409.

Signed-off-by: hasheddan georgedanielmangum@gmail.com

/cc @dims @liggitt

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.