Skip to main content
This course covered five core domains, dozens of tools, multiple hands‑on labs, and many demos — all designed to make you a confident platform engineer and ready for the CNPE exam. Below is a concise recap of each domain, how they integrate, and practical next steps to finalize your preparation. Section 1 — Platform architecture and infrastructure (15%)
  • Foundation concepts that support everything else on the platform.
  • Resource governance: pair ResourceQuota with LimitRange to control cluster‑ and namespace‑level resource consumption.
  • Persistent storage: manage lifecycle and reclamation using PersistentVolumeClaim (PVC), StorageClass, and reclaim policies.
  • Platform networking: understand how Service, Ingress / Gateway API, and service routing shape traffic flows.
  • Cost optimization: use tools such as OpenCost to identify waste and right‑size workloads for cost control.
A presentation slide titled "Section 1: Platform Architecture and Infrastructure (15%)" listing four numbered topics—Resource Governance, Persistent Storage, Platform Networking, and Cost Optimization—each with a short recommendation and a small icon. The notes mention using ResourceQuota/LimitRange, PVCs/StorageClasses, understanding Services/Ingress, and using OpenCost to right-size resources.
Although this domain is 15% of the exam, it underpins everything else: stable infrastructure, predictable resource usage, resilient storage, secure networking, and cost control. Section 2 — GitOps and delivery (25%)
  • GitOps principles: desired state management, drift detection, and repository design for predictable deployments. See GitOps fundamentals for patterns and best practices.
  • Argo CD: application objects, sync policies (manual vs automated), self‑heal and prune behaviors, and Helm/Helmfile integration.
  • CI/CD with Tekton: tasks, pipelines, and workspaces to produce reproducible builds and deployments.
  • Progressive delivery: implement canary releases and traffic shaping using Argo Rollouts and a service mesh such as Istio.
  • Troubleshooting delivery failures: diagnose pipeline logs, image/tag issues, and sync errors.
Section 3 — Extending Kubernetes (25%)
  • Treat APIs as products: design platform contracts and intuitive developer-facing APIs.
  • CRDs: author CustomResourceDefinitions with validation schemas, shortNames, versioning, and conversion strategies.
  • Operator patterns: implement reconcilers, handle exponential backoff, leader election, and common lifecycle patterns (example: cert‑manager).
  • Workflow orchestration: use Argo Workflows for DAGs, parameters, artifacts, and reusable workflow templates.
  • Crossplane compositions: map developer intent to real cloud infrastructure using Crossplane composites and claims.
Section 4 — Observability and operations (20%)
  • Metrics: collect and query metrics with Prometheus and PromQL; design alertable metrics and scrape targets.
  • Visualization: build operational and business dashboards with Grafana for signal‑based monitoring.
  • Alerting: configure Alertmanager for routing, silencing, grouping, and notification policies.
  • Tracing: instrument services with OpenTelemetry and analyze traces in Jaeger to understand request flows and latencies.
  • Incident response: practice triage, root‑cause analysis, remediation, and post‑incident validation with runbooks.
Slide titled "Section 4: Observability and Operations (20%)" showing a numbered list with icons. It lists Prometheus (metrics/PromQL), Grafana (dashboards), AlertManager (alerting/routing), Tracing (OpenTelemetry/Jaeger) and Troubleshooting (root cause analysis).
Section 5 — Security and policy (15%)
  • Identity and access: design fine‑grained RBAC roles and role bindings to enforce least privilege.
  • Admission control and policy: use Gatekeeper for complex Rego policies and Kyverno for YAML‑native validation, mutation, and generation.
  • Pod security: enforce Pod Security Standards (PSS) to restrict runtime privileges and capabilities.
  • Service‑to‑service security: enable mTLS and identity enforcement with a service mesh like Istio.
  • Supply chain security: scan images for vulnerabilities, implement signing for provenance, and enforce policies to reject unsigned or vulnerable images.
How it all connects
  • These five domains create a continuous platform lifecycle:
    1. Platform APIs and CRDs expose developer‑friendly primitives.
    2. GitOps delivery (Argo CD + CI pipelines) applies desired state to clusters.
    3. Observability (Prometheus/Grafana/Tracing) validates behavior and SLA compliance.
    4. Security/policy (Gatekeeper/Kyverno/PSS/mTLS) enforces guardrails and least privilege.
    5. Platform architecture (governance, storage, networking, cost) provides the stable foundation.
  • Developer experience: instead of tickets, developers request infrastructure via platform APIs; the platform reconciles the request and provisions cloud resources.
  • Delivery validation: observability tools confirm deployment behavior; progressive delivery strategies reduce blast radius.
  • Enforcement: admission controllers and policy engines prevent regressions and insecure configurations.
A slide titled "How It All Connects?" showing four colorful gear icons numbered 01–04. Each gear has a caption describing parts of a DevOps workflow: platform APIs, GitOps delivery to clusters, observability, and security/policy guardrails.
Quick reference — domain summary What to do next (practical steps)
Hands‑on practice is the most effective exam preparation. Run every lab, even those you think you’ve mastered — repetition improves speed, confidence, and recall under exam conditions.
  • Complete any hands‑on exercises you skipped; exam tasks closely mirror lab scenarios.
  • Practice for speed: time your labs, and aim to reduce completion time through repetition and checklisting.
  • Focus mock exams on your weak areas to convert weaknesses into strengths.
  • Review exam logistics and tips: time management, workspace navigation, and common pitfalls.
  • Schedule the exam confidently: trust your preparation, adhere to exam strategy, and allocate time for verification.
Links and references Thank you for taking this course. You’ve covered the key domains and practiced the essential tasks — you’re ready to earn the CNPE. Good luck!

Watch Video