EEdukron DevOps Library
KubernetesIntermediate16 submodules

Kubernetes Core Workloads

Expect questions about desired state, reconciliation, controller ownership, pod ephemerality, service discovery, selectors, rollout behavior, stateful identity, and node-level agents.

Interview focus

Answer with mechanism, evidence, and trade-offs

Expect questions about desired state, reconciliation, controller ownership, pod ephemerality, service discovery, selectors, rollout behavior, stateful identity, and node-level agents.

Strong-answer signals

  • 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 answer flow

Use this flow to structure design and scenario answers from context through evidence and recovery.

  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.

Practical interview scenario

Design, diagnose, and defend your decision

A deployment has unstable pod IPs, duplicated configuration, and a scheduled maintenance process running inside the web container. Redesign it with the appropriate Kubernetes objects.

A complete response should include
  • Business impact and technical constraints
  • Architecture or execution sequence
  • Identity, security, and evidence
  • Failure handling and recovery
  • Metrics and next improvement

Module question spotlight

Five questions to practise first

Model answers included
01Kubernetes architectureWhat problem does Kubernetes architecture solve, how does it work in Kubernetes Core Workloads, and what is it commonly confused with?

Define the mechanism and ownership boundary first. Explain that it defines the major responsibilities, boundaries, and control flow that engineers use before selecting an implementation detail, then contrast it with the adjacent responsibilities represented by the module prerequisites and the following Control plane concept. Close with a concrete validation signal.

02Control planeHow would you implement and validate Control plane for a production workload?

Start from workload constraints and existing state. Draw the components and ownership boundaries, trace one real request or change, and verify where state and control decisions live. Include identity, dependencies, normal and failure tests, monitoring, and an explicit recovery decision.

03Worker nodesA change involving Worker nodes causes a production symptom. What evidence would you inspect and how would you recover safely?

Establish scope and recent change, inspect the native configuration and event or log evidence, test the dependency boundary, apply the smallest reversible mitigation, verify user impact has recovered, and retain the findings for permanent prevention.

04PodsWhat problem does Pods solve, how does it work in Kubernetes Core Workloads, and what is it commonly confused with?

Define the mechanism and ownership boundary first. Explain that it provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle, then contrast it with the adjacent responsibilities represented by the preceding Worker nodes concept and the following ReplicaSets concept. Close with a concrete validation signal.

05ReplicaSetsHow would you implement and validate ReplicaSets for a production workload?

Start from workload constraints and existing state. State the requirement, configure the smallest working unit, connect its dependencies, test success and failure, and document operational ownership. Include identity, dependencies, normal and failure tests, monitoring, and an explicit recovery decision.

Complete question bank

48 topic-aware interview questions

16 submodules
03

Worker nodes

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
04

Pods

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
05

ReplicaSets

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
06

Deployments

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
07

Services

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
08

Namespaces

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
09

ConfigMaps

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
10

Secrets

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
11

Labels

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
12

Selectors

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
13

Jobs

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
14

CronJobs

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
15

StatefulSets

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set
16

DaemonSets

Concept, implementation, and troubleshooting questions with model answers, evaluation points, follow-ups, and weak-answer warnings.

Open question set