Comment by goltermann
Tuesday Sep 06, 2016 at 21:03 GMT

@quinton-hoole this is P2...time to punt to v1.5?

Comment by quinton-hoole
Tuesday Sep 06, 2016 at 21:29 GMT

@golterman Yes, 1.5 is fine. I seem to have lost the authority to update the Milestone? Did you perhaps change permissions?

Comment by goltermann
Tuesday Sep 06, 2016 at 21:38 GMT

I moved it - no idea why you wouldn't have permission on the kubernetes repo.

Comment by dims
Tuesday Nov 15, 2016 at 21:32 GMT

ok to move this to 1.6? please holler if not appropriate

Comment by quinton-hoole
Friday Nov 18, 2016 at 16:10 GMT

Reassigning to @nikhiljindal in case he wants to address this in future. @mfanjie would also be a suitable candidate.

Comment by ethernetdan
Monday Mar 13, 2017 at 22:30 GMT

Moving to 1.7 as late to happen in 1.6. Feel free to switch back if this is incorrect.

Comment by marun
Monday Jun 12, 2017 at 20:47 GMT

Not a release blocker for 1.7.

Comment by k8s-merge-robot
Saturday Sep 09, 2017 at 08:01 GMT

[MILESTONENOTIFIER] Milestone Removed

@nikhiljindal @quinton-hoole

Important:
This issue was missing labels required for the v1.8 milestone for more than 7 days:

kind: Must specify exactly one of [kind/bug, kind/cleanup, kind/feature].
priority: Must specify exactly one of [priority/critical-urgent, priority/important-longterm, priority/important-soon].

Removing it from the milestone.

cc @quinton-hoole

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

The issues have been addressed in current code after it was service controller code was refactored. So this issue is not relevant anymore
/close