DevOps Cost Discipline
Bridge DevOps and FinOps.
- Engineer
- 9
- 41
- 9
- ~7 hours
9 modules. 41 lessons. 9 quizzes.
M5.1 Tagging strategy that survives reorgs
Build a tagging scheme that survives a reorganisation, inherits rather than repeats, and is checked for drift.
Tagging strategy that survives reorgs
Build a tagging scheme that survives a reorganisation, inherits rather than repeats, and is checked for drift.
Tagging strategy that survives reorgs: module quiz
M5.2 Schedule design patterns
Build the schedule pattern each environment needs, including the ones that cannot simply be switched off.
Schedule design patterns
Build the schedule pattern each environment needs, including the ones that cannot simply be switched off.
Schedule design patterns: module quiz
M5.3 K8s cost discipline
Get Kubernetes cost under control, from requests and limits to autoscaler history, idle workloads and orphaned storage.
K8s cost discipline
Get Kubernetes cost under control, from requests and limits to autoscaler history, idle workloads and orphaned storage.
K8s cost discipline: module quiz
M5.4 Multi-account architecture for cost isolation
Use cloud accounts as a cost boundary. How to divide them, what to share, and what the network between them costs.
Multi-account architecture for cost isolation
Use cloud accounts as a cost boundary. How to divide them, what to share, and what the network between them costs.
Multi-account architecture for cost isolation: module quiz
M5.5 Reliability vs cost
Decide what reliability is worth per workload, and recognise the spending that protects nothing.
Reliability vs cost
Decide what reliability is worth per workload, and recognise the spending that protects nothing.
Reliability vs cost: module quiz
M5.6 IaC + cost
Catch cost and tagging problems in the pull request, and detect the drift that opens after it.
IaC + cost
Catch cost and tagging problems in the pull request, and detect the drift that opens after it.
IaC + cost: module quiz
M5.7 Incident response when cost is the incident
Handle the day cost becomes an emergency. What counts, who runs it, who hears what, and what changes afterwards.
Incident response when cost is the incident
Handle the day cost becomes an emergency. What counts, who runs it, who hears what, and what changes afterwards.
Incident response when cost is the incident: module quiz
M5.8 IaC governance
Gate your own Terraform and OpenTofu changes against a policy engine that decides but never enforces, including priced cost guardrails in the pull request.
IaC governance
Gate your own Terraform and OpenTofu changes against a policy engine that decides but never enforces, including priced cost guardrails in the pull request.
IaC governance: module quiz
M5.9 Cost work in the ticket system
Connect Jira, open tickets from recommendations manually or by policy, and keep recommendation status and ticket status in agreement without a polling cron.
Cost work in the ticket system
Connect Jira, open tickets from recommendations manually or by policy, and keep recommendation status and ticket status in agreement without a polling cron.