Industrialising: Kubernetes, Terraform, monitoring and cost control

Objectives

• Describe a cloud infrastructure as code with Terraform, versioned, reproducible and cleanly destroyed
• Deploy an application on Kubernetes (deployments, services, exposure, configuration, secrets) and make it scale automatically
• Set up observability (metrics, logs, traces, alerts) and a platform dashboard
• Define and test a backup, a restoration and a recovery plan on a loss scenario
• Analyse a cloud bill, identify waste (oversizing, forgotten resources, no reservations) and produce a quantified reduction plan

Audience

DevOps and platform engineers, cloud administrators, architects, IT managers of multi-application or multi-site companies.

Prerequisites

Have taken DEV-101 or use Docker and a cloud provider on a daily basis, with Git. Checked by a placement test.

Technical prerequisites

• One laptop per participant, 16 GB of memory recommended, with Docker, Git, Terraform and the Kubernetes command-line tool installed before the first day (procedure supplied with the invitation).
• Training Kubernetes cluster, cloud accounts and credits supplied by Yolea.
• For remote attendance, a stable connection of at least 10 Mbit/s, microphone and camera.
• The participant's own cloud bill accepted for the cost workshop, anonymised if necessary.

Skills covered

• Infrastructure as code
• Container orchestration
• Observability
• Continuity and recovery
• Financial management of the cloud

Programme

• 25% input, 75% hands-on workshops.
• One platform used throughout the course, built from scratch in code, on which an application is deployed, monitored, broken and then restored.
• Outage exercise on the third day.
• Cost workshop on real bills.
• Practical cases inspired by company situations (consolidated multi-site dashboard, mixed hosting with sensitive data at the client's site, monitoring of agents).
• Tools of the current edition: Terraform, Kubernetes, GitHub Actions, an open-source monitoring stack.
• Materials supplied: reference repository, reusable Terraform modules, manifest templates, recovery procedure, cost analysis grid, glossary.
• Personal action plan.
• Follow-up session after three weeks.

Format

21 hours, 3 consecutive days of 7 hours, or 2 + 1 days a week apart. In person recommended, hybrid possible; in-company or open enrolment; 8 to 12 participants.

Assessment

Beforehand, a placement test. During the course, check quizzes and an infrastructure code review. At the end, a practical challenge (rebuild a set platform from code, restore after a simulated outage, present a cost reduction plan, assessed against a grid), an immediate feedback evaluation and a named certificate of completion. After three weeks, a follow-up session.

The last exercise is an action plan: three real tasks that you leave ready to equip with tools.