Skip to main content
Text ready — video coming soon

Course 4

Building a service is only the beginning of keeping it useful. This course brings together the operation of the Python services, web interfaces and agents you met earlier in Stage 1.

DevOps connects developing software with operating it. Here, that means knowing how a change reaches users, how you notice a problem and how you recover.

This is a curriculum outline. The course's lessons are not available yet. Basic secrets, access, deployment and recovery appear earlier, before public use; this course deepens them.

The working module outline​

ModuleWhat you will learn to judge
Operate a Linux service and its networkWhere a process runs, how a request reaches it and which identity may access it
Automate and package repeatable environmentsWhether a script or container reliably recreates a setup you already understand
Deliver verified artifacts through a secure pipelineWhether automated checks produce the intended release and let you stop or reverse it
Describe and manage cloud infrastructureWhether a written configuration creates only the resources needed, with controlled access and cost
Observe and recover an operated serviceWhether logs and measurements reveal a failure, and whether the recovery procedure works
Read and deploy a small orchestrated workloadHow Kubernetes runs a small group of services, and how a Helm package describes its configuration

Each module combines the operating task, its supporting concepts and work on a real service. You learn these foundations before the final Kubernetes section. Module and chapter groupings may change as the teaching is written.

Depth and method​

Shared operations reach 2.0: you steer AI and check its decisions. Kubernetes and Helm are a bounded introduction at 1.5: identify the main pieces and follow a run. They are not a requirement for every small website.

You specify the intended operating behaviour, review AI's change and verify it independently. Evidence includes access checks, a controlled release, useful logs, a recovery attempt and the expected cost. A successful deployment alone does not prove that private data is safe or a backup can be restored.

The Stage 2 operations specialisation takes this further into larger systems, reliability and platforms other people use.