Our Container Cost Allocation project focuses on creating guidance and best practices to practitioners around allocating cost of containers.
This first output provides suggested container labels that are ready to use and can be combined into useful schemas. We also want this resource to encourage community debate about container cost allocation labeling, schemas, and best practices, inspiring contribution and future improvements.
During the September 2022 Summit, the Working Group presented their container cost allocation label schema tool.
Our group decided to transform the most important parts of that presentation into an interactive tool for our FinOps community.
How to use this resource
Use this interactive dictionary to learn common container labeling that the Working Group (WG) has sourced from community contributions. Use combinations of these dictionary cards to build out schemas, and to learn of possible mapping variants via “Label alias”, where similarly named labels might have similar purposes to one distinct label.
Click each filter to sort cards by the parameters that you choose.
Unclick filters to change how you’re sorting the cards, e.g. unclicking the crawl parameter will remove the filter seeking cards with the crawl label.
NOTE: Container Cost Allocation labeling and schema may greatly differ between different organizations with different use cases, goals, optimizations, and cloud service providers. The goal here is to provide an opinionated example about how to tackle the challenge of allocating container costs.
For hybrid and multi-cloud deployments, add a tag to identify the cloud service provider or data center where the container is running.
Context: Engineering and those who orchestrate containerization services
What kind of container labeling helps add information and context for run-stage executives? Contribute it here!
Context: Business organization
Common Resources: namespace, pod, deployment
Ways to contribute
FinOps practitioners can contribute in two ways. This collection of cards is maintained separately from the working group repository that handles more of the raw information and scripts. While we work on a future where we’ll source all of this content from one source of truth, everyone’s welcome to contribute to either of these repos.
Contributing to this repo edits the website content (the above cards)
Contributing to this repo edits source code examples and raw Working Group content
We apologize for this temporary complication as the FinOps Foundation team improves contribution processes. Feel free to fill out issues to communicate your recommendations or Make a Suggestion to suggest edits to the site.
Thanks for your patience as we improve how we welcome community contributions to our more advanced projects.
Help Wanted: User Stories!
We welcome any and all community user stories on how to best allocate and manage container costs at scale. User stories will be featured as links on all of these cards and be part of the greater FinOps Foundation collection of stories.
Here’s an example of a User Story and how it connects with other similar User Stories. These stories help us add practical real-world flavor to these Working Group projects, showing how real practitioners solve real FinOps problems.
Lastly, a big thank you to the FinOps Foundation support team for helping us bring our work to life: Ashley Hromatko (Staff Sponsor), Samantha White (Program Management), Tom Sharpe (Design), and Andrew Nhem (Content).