Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose load balancer status in service.status.loadBalancer #8992

Closed
thockin opened this issue May 29, 2015 · 5 comments
Closed

Expose load balancer status in service.status.loadBalancer #8992

thockin opened this issue May 29, 2015 · 5 comments
Labels
area/api Indicates an issue on api area. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@thockin
Copy link
Member

thockin commented May 29, 2015

We will soon emit events in case of error. Would be nice to add status info too. @justinsb
@thockin thockin added priority/backlog Higher priority than priority/awaiting-more-evidence. team/cluster labels May 29, 2015
@thockin thockin added this to the v1.0-post milestone May 29, 2015
@bgrant0607 bgrant0607 added the area/api Indicates an issue on api area. label May 29, 2015
@bgrant0607 bgrant0607 mentioned this issue Jun 2, 2015
Closed
@justinsb justinsb mentioned this issue Jun 3, 2015
Closed
@justinsb
Copy link
Member

justinsb commented Jun 3, 2015

v1-post means we're not targeting this for v1, right?

@bgrant0607
Copy link
Member

Correct

@bgrant0607 bgrant0607 mentioned this issue Jun 5, 2015
Closed
@bgrant0607 bgrant0607 removed this from the v1.0-post milestone Jul 24, 2015
@bprashanth bprashanth mentioned this issue Oct 13, 2015
Merged
@0xmichalis 0xmichalis added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed team/cluster (deprecated - do not use) labels Mar 20, 2017
@bgrant0607 bgrant0607 mentioned this issue Oct 25, 2017
Closed
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 22, 2017
@thockin
Copy link
Member Author

thockin commented Dec 23, 2017

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Dec 23, 2017
@thockin
Copy link
Member Author

thockin commented Dec 27, 2017

Dup of #52670 which has more details

@thockin thockin closed this as completed Dec 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/api Indicates an issue on api area. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@justinsb @0xmichalis @thockin @bgrant0607 @k8s-ci-robot @fejta-bot