config/jobs: add ci-test-infra-autobump-prowjobs-for-auto-deploy

[spiffxp]

Related:

• Part of: Migrate away from google.com gcp project k8s-testimages k8s.io#1523
• Part of: Decouple test image bumping from prow bumping #21137
• Related to: KEP: (sig-testing) Continuously Deploy K8s Prow enhancements#2539
• Followup to: config/prow: fix prow job autobump config #23597

We've been autobumping jobs separately from prow for a while now without incident. Let's start auto-deploying them.

This adopts a similar pattern that's used for prow's auto-deploys:

• 2 auto-deploy runs per day, during on-call hours
• hourly autobumps for humans to approve during on-call hours

See the comments on the jobs to see the rationale for scheduling

[spiffxp]

FYI @kubernetes/release-engineering
ref: #22831 (comment)

[spiffxp]

/cc @dims @ameukam

[pacoxu]

/lgtm

[justaugustus]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justaugustus, spiffxp

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/wg-k8s-infra/trusted/OWNERS [spiffxp]

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]

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

• key wg-k8s-infra-test-infra.yaml using file config/jobs/kubernetes/wg-k8s-infra/trusted/wg-k8s-infra-test-infra.yaml

In response to this:

Related:

• Part of: Migrate away from google.com gcp project k8s-testimages k8s.io#1523
• Part of: Decouple test image bumping from prow bumping #21137
• Related to: KEP: (sig-testing) Continuously Deploy K8s Prow enhancements#2539
• Followup to: config/prow: fix prow job autobump config #23597

We've been autobumping jobs separately from prow for a while now without incident. Let's start auto-deploying them.

This adopts a similar pattern that's used for prow's auto-deploys:

• 2 auto-deploy runs per day, during on-call hours
• hourly autobumps for humans to approve during on-call hours

See the comments on the jobs to see the rationale for scheduling

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.