Mahamed Ali

I'll open a separate PR to target the new jobs

/priority important-soon /sig testing

Datapoint: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kubetest2/236/pull-kubetest2-gce-build-up-down/1690009806422675456 Omitting build flag doesn't work because the shell scripts are looking for cloudprovider gcp binaries. ``` kubetest2 gce \ -v=2 \ --repo-root="$REPO_ROOT" \ --build \ --up \ --down...

5 tests are failing on the public ubuntu images. I'm going to open an issue in k/k for resolving the bugs/image config(I suspect it is most likely the cloud-init config...

This is ready to be merged after https://github.com/containerd/containerd/pull/8170 is merged. The tests pass when I use the same flags as the prowjobs. Flags ``` make test-e2e-node REMOTE=true REMOTE_MODE=gce IMAGE_CONFIG_FILE=~/k8s-test-infra/jobs/e2e_node/containerd/containerd-main/image-config.yaml FOCUS="\[NodeConformance\]"...

We also need to run a janitor on this new account, details are at https://github.com/kubernetes/test-infra/pull/30395#issuecomment-1681266966

https://docs.aws.amazon.com/waf/latest/developerguide/aws-managed-rule-groups-ip-rep.html In addition to what @puerco mentioned: 1. If you are an AWS customer at NYU, please reach out to Amazon and ask them to remove the NYU IP space...

/hold cancel

I drafted an email to send to the mailing lists. I think I can put it in a blog post too. https://docs.google.com/document/d/1-fAMIIZ9nLm4E6YJkRCYApFZZQl6RDaxMIlkt8EdR4I

Blog Post PR: https://github.com/kubernetes/website/pull/39214