Open spiffxp opened 3 years ago
/milestone v1.22
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
/remove-lifecycle stale Still relevant. Not going to freeze this though
/milestone v1.23
/milestone v1.24
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale /lifecycle frozen /milestone clear
Followup to https://github.com/kubernetes/k8s.io/pull/1534#discussion_r577999661
https://github.com/kubernetes/test-infra/pull/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