Each node has three bays: a StatefulSet's members with their own volume lockers at the back, a DaemonSet's agent in the middle, a Job's pods in front. A CronJob clock starts the Job on schedule. Or press ▶ Guided tour.
A StatefulSet's pods get stable names with an ordinal, are created and removed in order, and each gets its own PersistentVolumeClaim from a template, so a replaced db-1 comes back as db-1 with its data. A DaemonSet runs exactly one pod on every node, adding one when a node joins. A Job runs pods until enough succeed, retrying failures, and a CronJob creates Jobs on a cron schedule.