Comparison
DaemonSetvsResource request
DaemonSet
the log collector appears on every node automatically, including the one that joined the cluster four minutes ago.
A workload type that runs exactly one copy on every node, or every node matching a selector. It is how node-level infrastructure — log shippers, metrics agents, network plugins, storage drivers — is deployed, and it scales with the cluster rather than with traffic. Its capacity is easy to forget: each one takes CPU and memory from every node, so a fleet of five agents can quietly consume a meaningful fraction of what you are paying for.
Full entry →Resource request
you promise the scheduler the workload needs half a core, and that half core is subtracted from the node whether or not you ever use it.
The amount of CPU and memory a workload reserves, used by the scheduler to decide which nodes can hold it. It is a claim on capacity rather than a cap on usage, which is the distinction almost everyone gets wrong first. Requests set far above real usage are how a cluster ends up at thirty percent utilisation and a full bin at the same time, and requests set far below are how a node ends up oversubscribed and thrashing.
Full entry →