Clean up upgrade/downgrade test configs

[liggitt]

xref kubernetes/kubernetes#103697

• Removes solidly failing downgrade tests
• Changes stable1 / beta tests to use stable1 / latest, since the latest marker file is actually maintained
  • if there was already a stable1 / latest test, drop the stable1 / beta test
• Renames testgrid tabs to match reality of what is being tested (so we don't link to "1.13-1.14" tabs, which look obsolete)
• Adds human-readable job descriptions

/assign @spiffxp

[wojtek-t]

Why we're removing these?

[liggitt]

because the upgrade tests are the priority, and the downgrade tests are solidly failing (so no one is paying attention to the signal from them)

[wojtek-t]

/approve

Seems that bazel is failing.

[liggitt]

found/fixed a duplicate config and added job descriptions

[spiffxp]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, spiffxp, wojtek-t

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-cli/OWNERS [spiffxp,wojtek-t]
• config/jobs/kubernetes/sig-cloud-provider/OWNERS [spiffxp,wojtek-t]

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]

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

• key sig-cli-config.yaml using file config/jobs/kubernetes/sig-cli/sig-cli-config.yaml
• key gcp-gpu-upgrade-downgrade.yaml using file config/jobs/kubernetes/sig-cloud-provider/gcp/gpu/gcp-gpu-upgrade-downgrade.yaml
• key upgrade-gce.yaml using file config/jobs/kubernetes/sig-cloud-provider/gcp/upgrade-gce.yaml

In response to this:

xref kubernetes/kubernetes#103697

• Removes solidly failing downgrade tests
• Changes stable1 / beta tests to use stable1 / latest, since the latest marker file is actually maintained
• if there was already a stable1 / latest test, drop the stable1 / beta test
• Renames testgrid tabs to match reality of what is being tested (so we don't link to "1.13-1.14" tabs, which look obsolete)
• Adds human-readable job descriptions

/assign @spiffxp

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.

[spiffxp]

For anyone following along, a consequence of this is that it looks like we "lost" history from some of our infra's perspective (like testgrid or triage). Our infra doesn't understand the concept of renames, so they instead look like old jobs going away, and new jobs starting fresh with no history. The old job data necessary to regenerate history is still present in GCS, but it's at an old location not associated with the new job.

This is why testgrid shows a bunch of jobs with no results right now

[wojtek-t]

@liggitt @spiffxp - actually, it seems that something might have gone wrong - we still don't have any runs of those 3 days later...

[jberkus]

+1, downgrade tests have been poorly maintained to completely unmaintained since 1.13 or so. Ultimately, this is a signal that our community doesn't really care about downgrades, at least not for core canonical Kubernetes. If someone does care, maybe they'll step forwards to maintain the jobs.

[liggitt]

@liggitt @spiffxp - actually, it seems that something might have gone wrong - we still don't have any runs of those 3 days later...

that's... unexpected... did I miss something here?

[wojtek-t]

This is strange, because clearly I see some runs in prow:
https://prow.k8s.io/?job=ci-kubernetes-e2e-gce-stable1-latest-upgrade-cluster

It seems like testgrid-related issue...

[wojtek-t]

OK - it seems it works now