-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Documentation for opaque integer resources (alpha feature in 1.5) #1783
Conversation
Second, users must request the opaque resource in pods. | ||
|
||
To advertise a new opaque integer resource, the cluster operator should | ||
submit a `PATCH` HTTP request to the API server to specify the available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you should mention specifically that you patch the capacity, even though the next sentence mentions it.
quantity on a node in the cluster. After this operation, the node's | ||
`status.capacity` will include a new resource. The `status.allocatable` | ||
field is updated automatically with the new resource asychronously by | ||
the Kubelet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mention that it can be used in scheduling only once this happens.
LGTM I had two minor nits but since the doc deadline is very soon I think it's OK as is and you can fix that later. |
I can update this over the long weekend or submit a follow-up. Either way, will fix the comments. Thanks for the quick review.
… On Nov 24, 2016, at 00:12, David Oppenheimer ***@***.***> wrote:
LGTM
I had two minor nits but since the doc deadline is very soon I think it's OK as is and you can fix that later.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@davidopp addressed your comments (amended commit) |
cc @kubernetes/docs |
@@ -269,6 +269,86 @@ LastState: map[terminated:map[exitCode:137 reason:OOM Killed startedAt:2015-07-0 | |||
|
|||
We can see that this container was terminated because `reason:OOM Killed`, where *OOM* stands for Out Of Memory. | |||
|
|||
## Alpha Features |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ConnorDoyle @davidopp Did you also see the same?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup I see it this way too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you using the GHFM preview or viewing the netify rendered output (see https://deploy-preview-1783--kubernetes-io-vnext-staging.netlify.com/docs/user-guide/compute-resources/)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the same issue in github as others.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aveshagarwal please read my comment. Github markdown preview and jekyll aren't the same. Also, the point at which the rendering is broken isn't part of the change set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Current master looks the same when rendered with vanilla Github markdown preview (see https://github.com/kubernetes/kubernetes.github.io/blob/7112d4c53d8a6e34f3a43c8f4449403617f091e7/docs/user-guide/compute-resources.md#my-container-is-terminated)
@@ -269,6 +269,86 @@ LastState: map[terminated:map[exitCode:137 reason:OOM Killed startedAt:2015-07-0 | |||
|
|||
We can see that this container was terminated because `reason:OOM Killed`, where *OOM* stands for Out Of Memory. | |||
|
|||
## Alpha Features | |||
|
|||
### Opaque Integer Resources (Alpha Feature) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems weird to add "Alpha Feature" to the title when it's under the TOC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was following precedent set here: http://kubernetes.io/docs/user-guide/node-selection#node-affinity-alpha-feature
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One or the other. Either don't have an Alpha Features heading (and mark features Alpha), or don't include "Alpha" in each feature's individual heading.
Also, avoid nesting headings directly under one another; that's indicative of structural problems. If you have a header with nothing under it but another header, one or the other is not necessary.
|
||
The HTTP request below advertises 5 "foo" resources on node `k8s-node-1`. | ||
|
||
_NOTE: `~1` is the encoding for the character `/` in the patch path._ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is going to be confusing to users.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which part, this doc or the way slash is encoded in JSON-pointer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
slash encoding.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would a link to the JSON-pointer RFC help?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll never hear me say 'no' on the argument of add verbosity for clarity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, will add some more info about it (fact that JSON-patch makes use of JSON-pointer may be fairly niche)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
@@ -269,6 +269,86 @@ LastState: map[terminated:map[exitCode:137 reason:OOM Killed startedAt:2015-07-0 | |||
|
|||
We can see that this container was terminated because `reason:OOM Killed`, where *OOM* stands for Out Of Memory. | |||
|
|||
## Alpha Features | |||
|
|||
### Opaque Integer Resources (Alpha Feature) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One or the other. Either don't have an Alpha Features heading (and mark features Alpha), or don't include "Alpha" in each feature's individual heading.
Also, avoid nesting headings directly under one another; that's indicative of structural problems. If you have a header with nothing under it but another header, one or the other is not necessary.
|
||
### Opaque Integer Resources (Alpha Feature) | ||
|
||
Opaque integer resources were introduced as an alpha feature in Kubernetes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stick with present tense; no past or future.
"Kubernetes version 1.5 introduces Opaque integer resources. Opaque integer resources allow cluster operators to advertise new node-level resources that would be otherwise unknown to the system."
Move the last sentence: "So far only resource accounting is implemented" into a note about the Alpha state underneath the first paragraph, like so:
"Note: Opaque integer resources are Alpha in Kubernetes version 1.5. Only resource accounting is implemented; node-level isolation is still under active development."
@devin-donnelly thanks for the review comments, please take another look. |
Awesome, thanks. I can go ahead and merge this for 1.5. |
Feature issue: 76
Implementation PR: 31652
cc @kubernetes/sig-scheduling @timothysc
Also touches multiple instances of the API object path for pod containers. Can break this up into a separate commit/PR on request.
This change is