EEdukron DevOps Library
KubernetesIntermediate16 submodules

Kubernetes Core Workloads

Understand Kubernetes control-plane reconciliation and the workload resources used to run stateless, stateful, scheduled, and node-level applications.

How this module works

From concept to production evidence

Declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Learning outcomes

  • Explain control plane and worker-node responsibilities
  • Use pods, ReplicaSets, Deployments, and Services
  • Organize workloads with namespaces, labels, and selectors
  • Manage ConfigMaps, Secrets, Jobs, and CronJobs
  • Select StatefulSets or DaemonSets when their guarantees are required

Flow diagram

Kubernetes Core Workloads end-to-end flow

Use this sequence as the operating backbone for every submodule note and hands-on exercise.

  1. 01
    Submit manifestKubernetes Core Workloads stage 1: submit manifest with an auditable result before the next stage begins.
  2. 02
    Authenticate API requestKubernetes Core Workloads stage 2: authenticate api request with an auditable result before the next stage begins.
  3. 03
    Persist desired stateKubernetes Core Workloads stage 3: persist desired state with an auditable result before the next stage begins.
  4. 04
    Controller reconcilesKubernetes Core Workloads stage 4: controller reconciles with an auditable result before the next stage begins.
  5. 05
    Scheduler places podKubernetes Core Workloads stage 5: scheduler places pod with an auditable result before the next stage begins.
  6. 06
    Kubelet runs and reportsKubernetes Core Workloads stage 6: kubelet runs and reports with an auditable result before the next stage begins.

Integrated hands-on lab

Deploy multiple Kubernetes workload types

  1. Create namespace and configuration
  2. Deploy a stateless application and Service
  3. Run a Job and CronJob
  4. Deploy a StatefulSet or DaemonSet
  5. Inspect reconciliation and pod replacement

Complete module contents

16 full submodule notes

Read in order
01

Kubernetes architecture

Kubernetes architecture defines the major responsibilities, boundaries, and control flow that engineers use before selecting an implementation detail within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
02

Control plane

Control plane defines the major responsibilities, boundaries, and control flow that engineers use before selecting an implementation detail within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
03

Worker nodes

Worker nodes defines the major responsibilities, boundaries, and control flow that engineers use before selecting an implementation detail within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
04

Pods

Pods provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
05

ReplicaSets

ReplicaSets provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
06

Deployments

Deployments moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
07

Services

Services provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
08

Namespaces

Namespaces provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
09

ConfigMaps

ConfigMaps provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
10

Secrets

Secrets controls which actor may perform which action on which resource, under which conditions, with evidence that can be reviewed later within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
11

Labels

Labels provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
12

Selectors

Selectors provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
13

Jobs

Jobs provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
14

CronJobs

CronJobs provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
15

StatefulSets

StatefulSets preserves durable information with explicit ownership, consistency, access, lifecycle, replication, and recovery guarantees within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes
16

DaemonSets

DaemonSets provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Kubernetes Core Workloads. It is not an isolated definition: its value appears when it supports declare desired state through the API, let controllers reconcile it, expose stable service identities over replaceable pods, isolate workloads with namespaces, and externalize configuration from images.

Open full notes