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

Cloud Cost Monitoring for FinOps with OpenCost (LFS248)

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

Image
Image
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
Image
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
Image
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
Image Chapter 1. Course Introduction
Image Chapter 2. Introduction to Cloud Cost Monitoring Concepts
Image Chapter 3. The OpenCost Specification
Image Chapter 4. Introduction to OpenCost
Image Chapter 5. Installing OpenCost
Image Chapter 6. Configuring OpenCost for Cloud Providers (and On-Premises)
Image Chapter 7. Accessing the Data
Image Chapter 8: Prometheus and Grafana
Image Chapter 9. Deep Dive on Kubernetes Pricing
Image Chapter 10. Kubernetes Optimization Strategies
Image 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.