Cleanup and update releng/test_config.yaml

[xmudrii]

releng/test_config.yaml contains definitions for kubernetes/kubernetes tests (mainly periodics). We use those definitions to generate jobs for release branches when cutting a new release branch.

Over the time, this file has become unmaintained which is a huge risk for having jobs that are not properly testing release branches.

Here are some problems that I observed; this is a non exhaustive list, in other words, there might be other issues that I didn't observe:

• .jobs
  • ci-kubernetes-e2e-gce-cos-.+?-default is inconsistent
    • Different release branches has different args (to confirm if intentional)
      • Only ci-kubernetes-e2e-gce-cos-k8sbeta-default has --env=ENABLE_CACHE_MUTATION_DETECTOR=true arg
      • Only ci-kubernetes-e2e-gce-cos-k8sstable1-default has --env=ENABLE_POD_SECURITY_POLICY=true
      • Other ci-kubernetes-e2e-gce-cos-.+?-default jobs have no (additional args)
    • k8sbeta and k8sstable1 jobs are missing testgridNumFailuresToAlert parameter
  • We're missing betaapis tests for k8sbeta, k8sstable1, and k8sstable2 releases
    • Verify if args for betaapis tests are still valid
• .images
  • cos1, cos2, ubuntu1, and ubuntu2 images are not present in jobs names and therefore are likely unused (check if it is safe to remove these images)
• .testSuites
  • flaky, soak, stackdriver, updown, and nosat suites are not present in jobs names and therefore are likely unused (check if it is safe to remove these images)
• .nodeImages
  • cos1, cos2, ubuntu1, and ubuntu2 images are not present in jobs names and therefore are likely unused (check if it is safe to remove these images)
• .nodeTestSuites
  • gkespec and serial are likely unused

Once these issues are addressed, we should verify if arguments are up to date for remaining test options.

cc @kubernetes/release-engineering @dims

[xmudrii]

/sig release
/area release-eng

[xmudrii]

/priority important-soon

[dims]

/milestone v1.31

[k8s-ci-robot]

@dims: The provided milestone is not valid for this repository. Milestones in this repository: [someday, v1.24, v1.25]

Use /milestone clear to clear the milestone.

In response to this:

/milestone v1.31

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.