Free to read ยท Three levels

Kubernetes: declarative systems and reliable workloads

A complete path through Kubernetes architecture, Pods, services, configuration, storage, scheduling, RBAC, network policy, controllers, availability, security, autoscaling, and lifecycle diagnosis.

18 lessonsEnglish + ArabicContent reviewed
Start learning

In this course

Study eighteen developed lessons in three ordered levels. Trace a workload from declarative intent through execution, discovery, policy, and recovery. Each lesson includes two explained examples, three diagnostic mistakes, two worked exercises, objectives, takeaways, and specific primary references.

All manifests, fragments, and diagnostic records remain non-runnable. Verified Python simulations use only public synthetic in-memory values. The course never contacts a cluster, executes kubectl, fetches an image, changes a service, or performs cloud, administrative, security-scanning, or load operations. Namespace organization is explicitly distinguished from complete security isolation.

What you will learn

  • Explain desired state, controllers, execution, and service discovery with explicit ownership.
  • Interpret policy and lifecycle evidence without assuming unsupported guarantees.
  • Evaluate reliability, security, capacity, upgrades, and recovery as application-aware contracts.

Your learning path

Three levels

Basic: objects and execution boundaries

Understand architecture, identity, Pods, discovery, configuration, and storage as separate operational contracts.

  1. Architecture and declarative reconciliation
  2. Objects, labels, and namespaces
  3. Pods and workload controllers
  4. Services, endpoint selection, and DNS
  5. Configuration, Secrets, and workload identity
  6. Storage claims and data lifecycle
Explore this level

Intermediate: rollout, policy, and evidence

Connect rollout, probes, resources, authorization, network policy, and observability without overclaiming their guarantees.

  1. Deployments and rollout evidence
  2. Probes, startup, and graceful termination
  3. Resources and scheduling feasibility
  4. RBAC and service identities
  5. NetworkPolicy and traffic boundaries
  6. Observability and diagnostic evidence
Explore this level

Advanced: extensibility, resilience, and lifecycle

Reason about controllers, disruption, tenants, scaling, upgrades, and incident ownership under explicit assumptions.

  1. Controllers, custom resources, and Operators
  2. Availability and disruption budgets
  3. Workload security and multi-tenancy
  4. Autoscaling and capacity limits
  5. Cluster upgrades and API lifecycle
  6. GitOps ownership and incident diagnosis
Explore this level

Who this is for

  • Developers and platform learners who want precise Kubernetes models before operating workloads.
  • Technical collaborators investigating rollout, security, scheduling, or connectivity behavior.

Before you start

  • Basic containers, Linux, networking, and YAML familiarity; relevant boundaries are reviewed in context.
  • No cluster, kubeconfig, cloud account, administrative access, or external service is required.

Related technical solutions

CrashLoopBackOff: separate process exits from probe failureUse lifecycle evidence to distinguish invalid startup, resource termination, and health-check behavior before choosing a repair.Pending Pods: identify the unsatisfied scheduling contractSeparate placement, storage, and initialization evidence before changing requests, constraints, or capacity.Service connectivity: distinguish DNS, endpoints, and NetworkPolicyTrace a failed application connection through discovery, selection, policy, transport, and protocol without broad scans or unsafe exposure changes.