CI/CD
GitLab CI Blueprints for Multi-Stage Pipelines
Blueprint three production-grade pipelines with protected branches, child pipelines, and release artifacts you can reuse.
Stat focal
Core Node Surge runs cohorts for developers, release engineers, and platform crews who want pipeline-first evidence—not slide decks. Every capstone ends with annotated artifacts your on-call can trace.
Partner marks
Signal board
Runbooks peer reviewed in 2025 cycles
Municipal carrier POPs mirrored in lab racks
of surveyed clients would recommend mentor annotations
Languages supported across materials (EN primary)
Cross-org workflow tabletops hosted with partner crews
Every seat ships with annotated YAML, SBOM diffs, and retro templates tuned for Brazilian night windows. Mentors refuse vague praise—they cite the week where you hesitated on canary metrics.
Intake diagnostic on toolchain reality
Cohort kit shipped with runbooks
Weekly mentor annotations on diffs
Mid-capstone tabletop with partner script
Graduate artifact archive + office hour closeout
CI/CD
Blueprint three production-grade pipelines with protected branches, child pipelines, and release artifacts you can reuse.
Containers
Trace an image from Dockerfile to signed digest in a registry with SBOM attachments and policy checks.
Infrastructure Automation
Model three POP sites with reusable modules, remote state guardrails, and drift alarms that respect human reviewers.
“The Argo Rollouts week forced our release manager to rewrite canary queries tied to customer-visible latency—not CPU.”
Amanda Rocha · Delivery lead · Wholesale marketplace
“GitLab CI Blueprints lab clarified child pipelines for our contract tests.”
Iago M. · billing SaaS
Short verdict: SBOM diff worksheet is now attached to every promotion ticket.
Anonymous · observability SaaS
“Batch instrumentation course assumed Java/Golang stacks—mentors still reviewed our Kotlin traces, but slower.” Mild reservation, still worth it.
Isadora Melo
2025-08-12
Release managers rarely dispute graphs—they dispute the story. Here is how we tie Argo Rollouts queries to customer-visible symptoms.
2025-07-03
Handlers flap when operators cannot trace order of execution. We choreograph logging before touching idempotency tricks.
Do you run our production clusters? No. Mentors review manifests and logs you bring; we never ask for root on customer systems.
Are exams included? External vendor exams are not bundled; you receive completion letters with artifact links.
What if our stack is Windows-heavy? Several tracks assume Linux-first workflows; we disclose that per syllabus before invoices.
Drop a corporate address and we reply with PDF outlines plus mentor roster PDF—no automated phone trees.