Re: [kubernetes/kubernetes] Controllers keeps creating extra controllees if initialization is slow (#48893)
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Approval
@caesarxuchao @kubernetes/sig-api-machinery-bugs
Action required: This issue must have the status/approved-for-milestone label applied by a SIG maintainer. If the label is not applied within 6 days, the issue will be moved out of the v1.9 milestone.
sig/api-machinery: Issue will be escalated to these SIGs if needed.priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.kind/bug: Fixes a bug discovered during the current release.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Approval
Action required: This issue must have the status/approved-for-milestone label applied by a SIG maintainer. If the label is not applied within 5 days, the issue will be moved out of the v1.9 milestone.
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Approval
Action required: This issue must have the status/approved-for-milestone label applied by a SIG maintainer. If the label is not applied within 4 days, the issue will be moved out of the v1.9 milestone.
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Approval
Action required: This issue must have the status/approved-for-milestone label applied by a SIG maintainer. If the label is not applied within 2 days, the issue will be moved out of the v1.9 milestone.
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Approval
Action required: This issue must have the status/approved-for-milestone label applied by a SIG maintainer. If the label is not applied within 1 day, the issue will be moved out of the v1.9 milestone.
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Approval
Action required: This issue must have the status/approved-for-milestone label applied by a SIG maintainer. If the label is not applied within 0 days, the issue will be moved out of the v1.9 milestone.
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Removed
@caesarxuchao @kubernetes/sig-api-machinery-bugs
Important: This issue was missing the status/approved-for-milestone label for more than 7 days.
fejta-bot
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.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
fejta-bot
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
fejta-bot
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
k8s-ci-robot
Closed #48893.
Jordan Liggitt
alpha initializers feature removed in 1.14
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.