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

Creating External Loadbalancer should present some "progress status" #9106

Closed
jdk-google opened this issue Jun 2, 2015 · 7 comments
Closed

Creating External Loadbalancer should present some "progress status" #9106

jdk-google opened this issue Jun 2, 2015 · 7 comments
Assignees
@bowei
Labels
area/usability kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@jdk-google
Copy link

Creating an external loadbalancer takes minutes.

At the same time, the user doesn't know waht is happening, and whether it failed, is in progress, or just the user made a typo in the "externalLoadBalancer"

What we could do for example is:
in the "kubectl get services", if there is external Load Balancer configured, in the place of "external IP" show "status of the load balancer creation".
@bgrant0607
Copy link
Member

See also #8992

cc @thockin @justinsb @a-robinson

@bgrant0607 bgrant0607 added kind/enhancement priority/backlog Higher priority than priority/awaiting-more-evidence. area/usability labels Jun 2, 2015
@justinsb justinsb mentioned this issue Jun 3, 2015
Closed
@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
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 21, 2018
@bgrant0607
Copy link
Member

/remove-lifecycle rotten
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jan 22, 2018
@bgrant0607 bgrant0607 mentioned this issue Jan 23, 2018
Closed
@cmluciano
Copy link

Possible dupe of #52670

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. and removed kind/enhancement labels Jun 5, 2018
@thockin thockin added the triage/unresolved Indicates an issue that can not or will not be resolved. label Mar 8, 2019
@freehan freehan removed the triage/unresolved Indicates an issue that can not or will not be resolved. label May 16, 2019
@sftim sftim mentioned this issue Dec 21, 2022
Open
@sftim
Copy link
Contributor

sftim commented Dec 21, 2022

See #70159 (comment)

We'd ideally have someone willing to start of a KEP for the Networking SIG.

@thockin
Copy link
Member

thockin commented Dec 21, 2022

I think events are the API for progress-reports (we do report some already). It could probably be more but it's worth noting that there is a difference between "cloud LB created" and "cloud LB is accepting traffic". The former is sync, the latter is usually async.

I think this is a cloud-provider implementation detail feature-request, which should be handled in the out-of-tree cloud-providers as a convention, not requirement.

@thockin thockin closed this as completed Dec 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bowei bowei

Labels
area/usability kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. 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
10 participants
@bowei @freehan @0xmichalis @cmluciano @thockin @bgrant0607 @jdk-google @k8s-ci-robot @sftim @fejta-bot