Command Palette

Search for a command to run...

Hectal
Phase 6Advanced7 of 9 in CI/CD

Continuous Delivery & Deployment

Every deployment strategy, expressed as actual pipeline stages — and the organizational maturity question that actually decides how far to automate.

Phase 5 established that one specific, tested artifact should move through environments unchanged. This phase covers what happens at the very last step: how that artifact actually replaces what's currently running, the deliberate decision of how much of that process to automate versus gate with a human, and what a pipeline should do when a deployment turns out to be wrong.

0/4 · 0%
4 topics ~55 min 7 code blocks & diagrams
Start with the first topic
1
6.1

CD vs Continuous Deployment: The Real Organizational Decision

Topic 0.1 defined the difference between Continuous Delivery and Continuous Deployment — this topic covers what actually determines which one a team should genuinely choose, beyond just picking a definition.

13 min 1 diagram practice

2
6.2

Deployment Strategies, Expressed as Pipeline Stages

Recreate, rolling, blue-green, and canary are all genuine strategies for how a new version actually replaces the old one — each expressible as concrete pipeline stages, regardless of which platform is running them.

14 min 1 diagram 1 code practice

3
6.3

Approvals, Environment Gating & Feature Flags Together

Manual approvals (Phase 2.2, Phase 4.3) and feature flags (Topic 6.1) solve genuinely complementary problems — combining them gives a team both a fast, automatic deployment pipeline and deliberate, human-controlled feature releases.

14 min 1 diagram 1 code practice

4
6.4

Rollback Strategies in CI/CD

Every rollback mechanism this course has covered — kubectl rollout undo, helm rollback, redeploying a previous artifact — is a genuine option; a pipeline's real job is deciding, automatically or with a human, exactly when to use one.

14 min 1 diagram 1 code practice