audit followup: remove k8s-prow iam bindings for jobs that no longer run in k8s-prow #1674
Labels
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
sig/k8s-infra
Categorizes an issue or PR as relevant to SIG K8s Infra.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
Followup to #1534 (comment)
kubernetes/test-infra#19810 migrated some container image promoter jobs to k8s-infra-prow-build-trusted, we don't need k8s-prow to have workload identity bindings for these anymore
This is not intended to outright remove all k8s-prow bindings, some are likely still required for prow.k8s.io to schedule to the k8s-infra prow build clusters
/kind cleanup
/wg k8s-infra
/sig testing
/sig release
/area release-eng
/priority important-longterm
/milestone v1.21
The text was updated successfully, but these errors were encountered: