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.

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

ready/provisioned condition for v1/service #72746

Open
cppforlife opened this Issue Jan 9, 2019 · 2 comments

Comments

Projects
None yet
3 participants
@cppforlife
Copy link

cppforlife commented Jan 9, 2019

What would you like to be added:

it would be great if there would be a generic way to identify if v1/Service is done provisioning and ready to be used (not implying that endpoints are ready to be used; may be "ready" is not a good name for this).

Why is this needed:

when writing deployment software such as helm it would be nice to avoid having api client figure out when service is ready. example:

https://github.com/helm/helm/blob/4634f5f2faa0caa7de390c95c7d27be22d56a156/pkg/kube/wait.go#L212-L231

@cppforlife

This comment has been minimized.

Copy link

cppforlife commented Jan 9, 2019

/sig network

@k8s-ci-robot k8s-ci-robot added sig/network and removed needs-sig labels Jan 9, 2019

@phoenixking25

This comment has been minimized.

Copy link

phoenixking25 commented Jan 11, 2019

@cppforlife i am interested in this as i got the basic idea, but i am new to kubernetes codebase so need help for sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment