-
Notifications
You must be signed in to change notification settings - Fork 15.4k
Issue with k8s.io/docs/concepts/workloads/controllers/daemonset/ #17336
Copy link
Copy link
Closed
Labels
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Description
This is a Bug Report
Problem:
"A DaemonSet ensures that all eligible nodes run a copy of a Pod. Normally, the node that a Pod runs on is selected by the Kubernetes scheduler. However, DaemonSet pods are created and scheduled by the DaemonSet controller instead."
This is shown as the default option for a daemonset, but just above, it says the opposite is the default behavior.
Proposed Solution:
Change the default section or change this paragraph to show the correct behavior
Page to Update:
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.