Migrate to new prow cluster and cleanup unused secrets

[inteon]

First PR to migrate to the new prow cluster.

NOTE: the current master commit is https://github.com/cert-manager/testing/commit/472bbd48bf9ad2a6dcd3ba13b68395f8bdeabc8e. If we need to revert the prow migration, we can go back to that PR.

I would like to merge this PR as-is so we can continue testing all capabilities that require the master to be up-to-date (like the config auto updater).

[ThatsMrTalbot]

/lgtm

[inteon]

/approve

[cert-manager-prow[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: inteon

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](https://github.com/cert-manager/testing/blob/master/OWNERS)~~ [inteon] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[cert-manager-prow[bot]]

@inteon: Updated the following 3 configmaps:

• config configmap in namespace default at cluster default using the following files:
  • key config.yaml using file config/config.yaml
• job-config configmap in namespace default at cluster default using the following files:
  • key cert-manager-approver-policy-presubmits.yaml using file config/jobs/cert-manager/approver-policy/cert-manager-approver-policy-presubmits.yaml
  • key cert-manager-boilersuite.yaml using file config/jobs/cert-manager/boilersuite/cert-manager-boilersuite.yaml
  • key cert-manager-master.yaml using file config/jobs/cert-manager/cert-manager/master/cert-manager-master.yaml
  • key cert-manager-release-1.12.yaml using file config/jobs/cert-manager/cert-manager/release-1.12/cert-manager-release-1.12.yaml
  • key cert-manager-release-1.13.yaml using file config/jobs/cert-manager/cert-manager/release-1.13/cert-manager-release-1.13.yaml
  • key cert-manager-release-1.14.yaml using file config/jobs/cert-manager/cert-manager/release-1.14/cert-manager-release-1.14.yaml
  • key config.yaml using file config/jobs/cert-manager/config.yaml
  • key cert-manager-csi-driver-spiffe-presubmits.yaml using file config/jobs/cert-manager/csi-driver-spiffe/cert-manager-csi-driver-spiffe-presubmits.yaml
  • key cert-manager-csi-driver-presubmits.yaml using file config/jobs/cert-manager/csi-driver/cert-manager-csi-driver-presubmits.yaml
  • key cert-manager-csi-lib-presubmits.yaml using file config/jobs/cert-manager/csi-lib/cert-manager-csi-lib-presubmits.yaml
  • key cert-manager-issuer-lib-presubmits.yaml using file config/jobs/cert-manager/issuer-lib/cert-manager-issuer-lib-presubmits.yaml
  • key cert-manager-istio-csr-presubmits.yaml using file config/jobs/cert-manager/istio-csr/cert-manager-istio-csr-presubmits.yaml
  • key cert-manager-release-presubmits.yaml using file config/jobs/cert-manager/release/cert-manager-release-presubmits.yaml
  • key trust-manager-presubmits.yaml using file config/jobs/cert-manager/trust-manager/trust-manager-presubmits.yaml
  • key testing-periodics-trusted.yaml using file config/jobs/testing/testing-periodics-trusted.yaml
  • key testing-postsubmits-trusted.yaml using file config/jobs/testing/testing-postsubmits-trusted.yaml
  • key testing-presets-trusted.yaml using file config/jobs/testing/testing-presets-trusted.yaml
• label-config configmap in namespace default at cluster default using the following files:
  • key labels.yaml using file config/labels.yaml

In response to [this](https://github.com/cert-manager/testing/pull/978): >First PR to migrate to the new prow cluster. > >NOTE: the current master commit is https://github.com/cert-manager/testing/commit/472bbd48bf9ad2a6dcd3ba13b68395f8bdeabc8e. >If we need to revert the prow migration, we can go back to that PR. > >I would like to merge this PR as-is so we can continue testing all capabilities that require the master to be up-to-date (like the config auto updater). Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.