Training & Certification

Training > Cloud & Containers > Cloud Cost Monitoring for FinOps with OpenCost (LFS248)

Training Course

Discover FinOps and cloud cost management with OpenCost, empowering your decision-making with key metrics.

Who Is It For

This course is intended for engineers, developers, and system administrators with concerns over the cost and efficiency of their Kubernetes deployments.

read less read more

What You’ll Learn

Learn the basics of Kubernetes and cloud cost monitoring for FinOps practices. Optimize Kubernetes deployments for cost efficiency and install OpenCost and explore accessing data gathered through APIs, exports, and Prometheus.

read less read more

What It Prepares You For

This course will provide a foundational understanding of container costs across cloud providers, working with data captured by OpenCost to track costs for FinOps and optimization practices.

read less read more

Course Outline

Chapter 1. Course Introduction

Chapter 2. Introduction to Cloud Cost Monitoring Concepts

Chapter 3. The OpenCost Specification

Chapter 4. Introduction to OpenCost

Chapter 5. Installing OpenCost

Chapter 6. Configuring OpenCost for Cloud Providers (and On-Premises)

Chapter 7. Accessing the Data

Chapter 8: Prometheus and Grafana

Chapter 9. Deep Dive on Kubernetes Pricing

Chapter 10. Kubernetes Optimization Strategies

Chapter 11. OpenCost as an Open Source Project

Prerequisites

To make the best of this course, students are expected to have:

Familiarity with the fundamental concepts of Kubernetes and public clouds.
Hands-on experience using command line tools and working with APIs.
Familiarity with Prometheus and Grafana, but expertise is not required.

Lab Info

Students will need access to the public cloud consoles of their choice for finding and configuring the required permissions if they wish to follow the cloud provider examples.

Access to a Kubernetes cluster with sufficient permissions for managing OpenCost will be necessary for hands-on testing and working with examples. Kind may be used as an on-premises equivalent if no public cloud deployments are available.