kops grid: create serial test for flaky scenario

[justinsb]

Hoping to diagnose out why tests are timing out.

Issue #20738

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb

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/kops/OWNERS [justinsb]

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

[justinsb]

/retest

bazel flake:

2021/02/04 16:31:26 Image pull was unsuccessful: unable to save remote image gcr.io/k8s-testimages/launcher.gcr.io/google/bazel@sha256:e006f1c3658dd11d5176d5f7a862df4d5b9c06cfe014d5b8a86bb64b20a6f8be: unable to write image layers: unable to write image layer: unable to write the contents of layer 0 to /bazel-scratch/.cache/bazel/_bazel_root/05618a594cb3499a4b912817865867cd/external/bazel-base/image/000.tar.gz: read tcp 10.60.56.100:38508->74.125.132.128:443: read: connection reset by peer

[hakman]

/lgtm

[k8s-ci-robot]

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

• key kops-periodics-grid.yaml using file config/jobs/kubernetes/kops/kops-periodics-grid.yaml

In response to this:

Hoping to diagnose out why tests are timing out.

Issue #20738

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.