switch to the new prow image registry

[upodroid]

kubernetes/test-infra#33210

Prow has been out of date because Kubernetes changed the prow image location.

The bumper should run successfully on the next run
bumper job: https://prow.knative.dev/job-history/gs/knative-prow/logs/ci-knative-prow-auto-bumper-for-auto-deploy

[cardil]

/lgtm

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cardil, upodroid

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:

• OWNERS [cardil,upodroid]

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

[knative-prow]

@upodroid: Updated the following 2 configmaps:

• config configmap in namespace default at cluster default using the following files:
  • key config.yaml using file prow/config.yaml
• job-config configmap in namespace default at cluster default using the following files:
  • key autobump-flaky-test-reporter.yaml using file prow/jobs/custom/autobump-flaky-test-reporter.yaml
  • key autobump-prow-tests.yaml using file prow/jobs/custom/autobump-prow-tests.yaml
  • key autobump-prow.yaml using file prow/jobs/custom/autobump-prow.yaml
  • key autodeploy-prow.yaml using file prow/jobs/custom/autodeploy-prow.yaml
  • key branchprotector.yaml using file prow/jobs/custom/branchprotector.yaml
  • key infra.yaml using file prow/jobs/custom/infra.yaml
  • key label-sync.yaml using file prow/jobs/custom/label-sync.yaml
  • key peribolos.yaml using file prow/jobs/custom/peribolos.yaml

In response to this:

kubernetes/test-infra#33210

Prow has been out of date because Kubernetes changed the prow image location.

The bumper should run successfully on the next run
bumper job: https://prow.knative.dev/job-history/gs/knative-prow/logs/ci-knative-prow-auto-bumper-for-auto-deploy

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-sigs/prow repository.