-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Job and DaemonSet documentation. #14079
Conversation
Labelling this PR as size/L |
GCE e2e build/test failed for commit 70cab5d36834ce3a6cdd7bc1b5c51d8c30a1e5b0. |
Ugh. Somehow update-generated-docs.sh presubmit deleted all my documentation text. |
Labelling this PR as size/L |
@erictune if you ever committed it, you should be able to get it back, even if you rebased it away. |
Sorry I meant #13368 |
GCE e2e build/test passed for commit 606374d5b7a4787a8aa458b0f8e7178b0c1d9b8f. |
Labelling this PR as size/XL |
GCE e2e build/test passed for commit 669a19315eb02a4e42c0a63dae19c517f45e12df. |
@kubernetes/rh-cluster-infra |
GCE e2e build/test passed for commit 2852df8762158b01d9e6a8ed47cbe2619ea3c1e6. |
@mikedanese @soltysh @AnanyaKumar this is ready for you to take a look at it |
GCE e2e build/test passed for commit 48bcd0cac6f4f290e1c6996b068bbfad6dd0dd2c. |
Note that we're also going to be submitting Ananya's original design doc (#14326) but your doc makes sense as the user-consumable documentation. |
GCE e2e build/test passed for commit 4db983ae62fb995081ebff12f0bd453f01c38107. |
@davidopp Sorry for slow response. Yes, this was meant to user-focused and task-oriented -- a complement to the design doc. |
Now you have my 100% LGTM 😄 |
@k8s-oncall this is only docs and test code and comments. You may merge despite free if you like. |
## How Daemon Pods are Scheduled | ||
|
||
Normally, the machine that a pod runs on is selected by the Kubernetes scheduler. However, pods | ||
create by the Daemon controller have the machine already selected (`.spec.nodeName` is specified |
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.
pods created by
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.
fixed
are called [static pods](static-pods.md). | ||
Unlike DaemonSet, static pods cannot be managed with kubectl | ||
or other Kubernetes API clients. Static pods do not depend on the apiserver, making them useful | ||
in cluster bootstrapping cases. Also, static pods may be deprecated in the future. |
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 need to verify this, but if your cluster rejects the ability to run privileged containers in the api-server, you could have a configuration where the kubelet enables the ability to run privileged containers. As a result, you could have a configuration where the use of static pods could be enabled to support running a privileged container, but the daemonset would be rejected from running a privileged container.
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.
Yes, I think you could have that situation.
GCE e2e build/test passed for commit 86ee4b6a8ba4a943856c0aeb1861bf21a9825ae1. |
Needs rebase |
metadata: | ||
name: prometheus-node-exporter | ||
labels: | ||
name: prometheus-node-exporter |
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.
Please don't use "name" as a label key.
https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/config-best-practices.md
How about something like daemon: monitoring
? If I were a cluster admin, I'd probably use the same label key for all my node agents / daemons, but not name
. name
is too generic (it could overlap with non-daemon pods) and confusing for users (due to similarity with metadata.name).
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.
fixed.
GCE e2e build/test passed for commit 1c168e422bbe71f51df2746ff0c43891bfdcb7f0. |
Fixed to use |
GCE e2e build/test passed for commit bf9e932. |
Job and DaemonSet documentation.
Not ready for final review, but putting this out there so people know I am working on it.