Update how ci-operator gets cluster profile secrets
Use config-resolver to get the name of cluster profile secret we need, instead of mounting it to the job and then reading it locally along with the other user-defined secrets.
Next steps:
- create a presubmit job to check the cluster profile secret (defined in the test config) exists in the ci namespace
- edit prowgen so it doesn't add the cluster profile volume to the job yaml, as it won't be needed anymore & regenerate all jobs
/cc @droslean
/retest
/test remaining-required
/test e2e
/test e2e
/test e2e
/test e2e
/test e2e
/test e2e
/test e2e
/test e2e
/test e2e
/label tide/merge-method-squash
/test e2e
/hold to synchronize with rolling out of the other changes that need to be done
/test remaining-required
/test remaining-required
/retest-required
/retest
/test e2e
/test e2e
/lgtm
/hold cancel
/retest-required
/retest
/test checkconfig
/hold I want to wait until tomorrow morning so I'm present to resolve any issues
/retest
/test e2e
/test e2e
/test images