-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Mark QoS as an experimental feature #15317
Conversation
Just referring to offline discussion is not helpful. Should have at least referenced the prior PR: #14943. Please add the references mentioned in the previous PR. Citing the split hierarchy issue as an example would help people understand why it's not fully baked. This is too terse. |
Labelling this PR as size/XS |
GCE e2e test build/test passed for commit 7ae9560b010fbf4a6f1f9bf374861a6cbf2fb027. |
b268c1b
to
38e813f
Compare
Labelling this PR as size/M |
GCE e2e test build/test passed for commit b268c1b7e5cf7acbf67e4262287e2fa95d414313. |
GCE e2e test build/test passed for commit 38e813f9bea5f5319aa02cc375d8bbfb8b18021e. |
@bgrant0607: Updated the PR to include a few major issues. |
GCE e2e test build/test passed for commit 955f896. |
LGTM On Thursday, October 8, 2015, Kubernetes Bot notifications@github.com
|
Ok. |
Automatic merge from submit-queue |
Auto commit by PR queue bot
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Auto commit by PR queue bot
@bgrant0607: Updated doc as discussed offline.
Given that #14943 is still under debate, I have opened this PR to mark QoS as an experimental feature in v1.1. I intend to cherry-pick this PR into the v1.1 release branch.
cc @derekwaynecarr