Which Kubernetes cluster logging architecture uses a single agent per Kubernetes node to aggregate and stream stdout and stderr logs from containers to a backend log collection service?

Ship logs is not a recognized or defined Kubernetes logging architecture pattern in Kubernetes documentation and does not correspond to a standard deployment approach.

A sidecar container with a logging agent runs a dedicated logging container alongside the application container within the same pod, which is a per-pod pattern rather than a single-agent-per-node aggregation architecture.

The node-level logging agent architecture deploys one logging agent such as Fluentd or Fluent Bit per Kubernetes node via a DaemonSet; the agent reads container log files written by the container runtime to the node's filesystem and streams them to a log aggregation backend without requiring any modifications to application pods or their configurations.

A sidecar container alone (without a dedicated logging agent) is a pattern where a second container in the pod re-streams the application's log files, but this does not use a single agent per node and does not aggregate logs across all pods on the node.