Re: [kubernetes/kubernetes] Determine if resource.NewHelper calls are superseded by dynamic client (#65494)
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue Needs Approval
@juanvallejo @soltysh @kubernetes/sig-cli-misc
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.12 milestone.
sig/cli: 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/cleanup: Adding tests, refactoring, fixing old bugs.
—
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 3 days, the issue will be moved out of the v1.12 milestone.
Maciej Szulik
/status approved-for-milestone
Kubernetes Submit Queue
[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process
sig/cli: 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/cleanup: Adding tests, refactoring, fixing old bugs.
—
Davanum Srinivas
@juanvallejo @soltysh Do we clear the v1.12 milestone?
Maciej Szulik
@dims yeah, let's move it to the next milestone.
Davanum Srinivas
/milestone clear
Davanum Srinivas
oops
/milestone v1.13
Niko Pen
@juanvallejo @soltysh ping, is this WIP for 1.13? any related PR?
Maciej Szulik
Yes, this is still open and in-progress, but not something that we will actually finish for 1.13, it'll take us some more time.
Niko Pen
/milestone clear
Niko Pen
/milestone v1.14
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.
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
Ibrahim AshShohail
Hey!
Gentle reminder that code freeze for 1.14 is this Thursday.
Since this is part of the 1.14 milestone, is it going to be resolved soon? If not, let's clear the milestone.
Maciej Szulik
@ibrasho hey, sorry, this is not targeted at 1.14 but more of a long term goal. Lemme clear the milestone.
/milestone clear
/remove-lifecycle rotten
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.
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
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
Kubernetes Prow Robot
Closed #65494.
Kubernetes Prow Robot
@fejta-bot: Closing this issue.
In response to this:
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
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.