Update Prow to v20231027-9cda73bb73

[knative-prow-updater-robot]

Multiple distinct gcr.io/k8s-prow/ changes:

Commits	Dates	Images
kubernetes/test-infra@811baf2...9cda73b	2023‑10‑19 → 2023‑10‑27	branchprotector, checkconfig, cherrypicker, clonerefs, config-bootstrapper, configurator, crier, deck, entrypoint, generic-autobumper, ghproxy, hook, horologium, initupload, label_sync, mkpj, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

No gcr.io/k8s-staging-boskos/ changes.

/cc

[knative-prow]

@knative-prow-updater-robot: GitHub didn't allow me to request PR reviews from the following users: knative-prow-updater-robot.

Note that only knative members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Multiple distinct gcr.io/k8s-prow/ changes:

Commits	Dates	Images
kubernetes/test-infra@811baf2...9cda73b	2023‑10‑19 → 2023‑10‑27	branchprotector, checkconfig, cherrypicker, clonerefs, config-bootstrapper, configurator, crier, deck, entrypoint, generic-autobumper, ghproxy, hook, horologium, initupload, label_sync, mkpj, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

No gcr.io/k8s-staging-boskos/ changes.

/cc

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.

[knative-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: knative-prow-updater-robot
Once this PR has been reviewed and has the lgtm label, please assign kvmware for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[knative-prow]

@knative-prow-updater-robot: 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:

Multiple distinct gcr.io/k8s-prow/ changes:

Commits	Dates	Images
kubernetes/test-infra@811baf2...9cda73b	2023‑10‑19 → 2023‑10‑27	branchprotector, checkconfig, cherrypicker, clonerefs, config-bootstrapper, configurator, crier, deck, entrypoint, generic-autobumper, ghproxy, hook, horologium, initupload, label_sync, mkpj, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

No gcr.io/k8s-staging-boskos/ changes.

/cc

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.