THE CATALOG
Eleven programs. One standard: production-grade.
Every program is delivered privately for your organization, hands-on, on live environments.
FOUNDATIONS
Focused entry points
Kubernetes Production Failures — Troubleshooting Masterclass 1 day · Intermediate
Audience: Platform, operations, SRE, and development teams running workloads on Kubernetes.
Prerequisites: Working familiarity with Kubernetes objects and kubectl.
Format: Incident-driven. Every module recreates a real production failure live in a lab cluster; participants diagnose before the instructor resolves.
Outcomes: Apply a systematic triage method to any failing workload or cluster · Read the signals: events, conditions, controller behavior · Resolve the failure classes that cause most production pain — scheduling, crashes, networking, upgrades · Leave with a reusable troubleshooting runbook.
Agenda — Morning: Scheduling failures: taints and tolerations, topology spread, resource pressure, node selectors · Workload crashes: CrashLoopBackOff, OOMKills, probe misconfiguration. Afternoon: Networking failures: DNS, service routing, connection exhaustion · Upgrade blockers: PodDisruptionBudgets and drain failures · Admission and policy failures · War-room methodology and closing runbook.
GameDay: Incident Simulation 1 day · Intermediate–Advanced
Audience: Existing operations, platform, or SRE teams — delivered as a team exercise.
Prerequisites: The team operates Kubernetes or cloud infrastructure in production today.
Format: A controlled environment is deliberately broken in escalating rounds. The team responds as it would in production; instructors observe, guide, and score.
Outcomes: Measured view of the team's real incident response · Exposure of process gaps that never show up in classroom training · A scored debrief and management readout.
Agenda — Morning: Briefing and rules of engagement · Round 1: single-component failure · Round 2: cascading failure under time pressure. Afternoon: Round 3: ambiguous multi-cause incident · Team debrief against the scoring rubric · Management readout.
CORE PLATFORM
The engineering backbone
Kubernetes for Operations Teams (AKS / EKS) 3 days · Foundation → Production
Audience: Operations and infrastructure engineers taking ownership of managed Kubernetes.
Prerequisites: Linux command-line proficiency; containers helpful but not required.
Format: Roughly 60% hands-on labs on a live managed cluster.
Outcomes: Deploy, expose, scale, and update applications with confidence · Operate the cluster: upgrades, capacity, access control, monitoring · Troubleshoot common failure classes independently · Apply a production-readiness checklist.
Agenda — Day 1: Architecture and core objects · Deployments and rollouts · Configuration and secrets · Services. Day 2: Ingress · Storage and stateful workloads · RBAC · Scheduling: requests, limits, taints, affinity. Day 3: Upgrades and node management · Monitoring and logging · Troubleshooting workshop · Production-readiness review.
OpenShift Administration in Production 3 days · Foundation → Production
Audience: Enterprise operations teams running — or adopting — Red Hat OpenShift on-premises or hybrid.
Prerequisites: Linux administration; Kubernetes exposure helpful.
Format: Hands-on labs on a dedicated OpenShift environment. Curriculum maps to EX280 exam-readiness.
Outcomes: Administer projects, users, and role-based access · Operate Routes, storage, and the operator ecosystem · Run day-2 operations: monitoring, logging, upgrades, backup · Harden the platform for enterprise and regulatory expectations.
Agenda — Day 1: Platform architecture · The oc workflow and web console · Projects and multi-tenancy · Authentication and Security Context Constraints. Day 2: Networking and Routes · Persistent storage · Operators and OperatorHub · Builds, image streams, registries. Day 3: Monitoring and logging stack · Cluster upgrades · Backup and disaster recovery · Hardening and compliance review · EX280 readiness mapping.
Terraform & Infrastructure-as-Code in Production 3 days · Foundation → Production
Audience: Infrastructure and platform engineers standardizing on IaC (Azure or AWS flavor).
Prerequisites: Working knowledge of the target cloud platform.
Format: Progressive labs building toward a production-grade module structure with remote state and CI integration.
Outcomes: Write clear, maintainable Terraform · Structure code with modules and manage state safely across a team · Integrate Terraform into CI/CD with review and policy gates · Import and refactor existing infrastructure without breakage.
Agenda — Day 1: HCL and provider fundamentals · Resources, data sources, dependencies · State · Variables and outputs. Day 2: Modules and composition · Remote state and locking · Environments and workspaces · Repository structure at team scale. Day 3: Terraform in CI/CD · Policy, drift, and review workflows · Secrets handling · Importing and refactoring live infrastructure.
GitOps with Argo CD 2 days · Intermediate
Audience: Teams running Kubernetes or OpenShift who want deployments driven from Git. (On OpenShift, delivered against OpenShift GitOps — the same engine.)
Prerequisites: Kubernetes fundamentals; Git proficiency.
Format: Labs progress from first application to a full multi-environment promotion model.
Outcomes: Operate Argo CD as the deployment engine for a real cluster · Design repository layouts and promotion flows that scale · Handle secrets, access control, and drift · Recover the platform from Git after simulated loss.
Agenda — Day 1: GitOps principles and architecture · Applications and sync strategies · Repository layout patterns · Health, hooks, sync waves. Day 2: App-of-apps and ApplicationSets · Multi-environment promotion · Secrets in GitOps · RBAC and SSO · Drift and disaster-recovery exercise.
REGULATED & ADVANCED
For environments where failure is expensive
DevSecOps for Regulated Industries 3 days · Intermediate–Advanced
Audience: Engineering and security teams in banking, fintech, telecom, and other audited environments.
Prerequisites: CI/CD familiarity; Kubernetes exposure recommended.
Format: Built around a reference pipeline progressively secured across three days; controls mapped to common regulatory expectations.
Outcomes: Embed scanning — code, dependencies, containers — into pipelines without stalling them · Enforce policy-as-code with admission control · Manage secrets across the delivery lifecycle · Map technical controls to audit requirements.
Agenda — Day 1: Threat-modeling the delivery pipeline · Secure SDLC · Static, dependency, and container scanning. Day 2: Policy-as-code and admission control (Kyverno / OPA) · Image signing and supply-chain integrity · Secrets management architecture. Day 3: Kubernetes hardening against CIS benchmarks · Runtime security signals · Mapping controls to audit requirements · Compliance-readiness review.
Observability & SRE Practices 2 days · Intermediate
Audience: Operations and platform teams moving from reactive monitoring to engineered reliability.
Prerequisites: A production system the team is responsible for; Kubernetes helpful.
Format: Day one builds the observability stack hands-on; day two applies SRE practice to the team's own services.
Outcomes: Build metrics, dashboards, and alerting people trust · Define SLIs, SLOs, and error budgets · Run on-call, incidents, and postmortems as repeatable practice · Leave with an alerting standard and incident process template.
Agenda — Day 1: Metrics and Prometheus · Dashboards that answer questions (Grafana) · Alerting design and fatigue · Logs and correlation. Day 2: SLIs, SLOs, error budgets · On-call and incident management · Postmortem practice · OpenTelemetry: where tracing fits.
CERTIFICATION INTENSIVES
When certification is the KPI
CKA — Certified Kubernetes Administrator Intensive 5 days · Certification prep
Audience: Engineers targeting the CKA credential with a defined exam window.
Prerequisites: Hands-on Kubernetes exposure; this is an intensive, not an introduction.
Format: Aligned to the current CNCF exam curriculum. Timed practical drills daily; two full mock exams under exam conditions.
Outcomes: Cover every CKA exam domain hands-on · Build the speed and kubectl fluency the practical exam demands · Benchmark readiness through scored mock exams.
Agenda — Days 1–2: Cluster architecture, installation, configuration · Workloads and scheduling · Daily timed drills. Days 3–4: Services and networking · Storage · Troubleshooting deep-dive · Daily timed drills. Day 5: Full mock exams under exam conditions · Gap review and exam strategy.
AZ-104 — Microsoft Azure Administrator Intensive 5 days · Certification prep
Audience: IT professionals administering Azure environments targeting AZ-104.
Prerequisites: General IT administration experience; Azure exposure helpful.
Format: Aligned to the current Microsoft exam objectives, with labs in a live Azure environment and practice assessments throughout.
Outcomes: Administer identity, governance, storage, compute, and networking on Azure · Apply the material through labs mapped to exam objectives · Benchmark readiness with practice assessments.
Agenda — Days 1–2: Identity and governance: Entra ID, RBAC, policy · Storage accounts and data protection. Days 3–4: Compute: VMs, containers, App Service · Virtual networking, DNS, load balancing · Backup and monitoring. Day 5: Practice assessment under exam conditions · Gap review and exam strategy.
AZ-400 — Azure DevOps Engineer Intensive 5 days · Certification prep
Audience: Engineers designing delivery pipelines on Azure targeting AZ-400.
Prerequisites: AZ-104-level Azure knowledge or equivalent experience.
Format: Aligned to the current Microsoft exam objectives; labs build a complete delivery pipeline across the week.
Outcomes: Design and implement source control, pipelines, and release strategies on Azure DevOps and GitHub · Integrate IaC, security, and compliance into delivery · Benchmark readiness with practice assessments.
Agenda — Days 1–2: DevOps processes and source control strategy · Build pipelines and artifact management. Days 3–4: Release strategy and deployment patterns · IaC integration · Security, compliance, and secrets in pipelines. Day 5: Monitoring and feedback · Practice assessment · Gap review and exam strategy.
ADDITIONAL PROGRAMS
Additional programs — outlines on request
The next step is one day
Book an Ignite day: one hands-on workshop for your team, a skills snapshot, and a written readout — at a fixed, published price of EGP 25,000. If it does not meet your expectations, you do not pay. One conversation is enough to scope it.
Book an Ignite Day