Introducing Kubemodel blog post #441
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spa-raj
commented
Dec 3, 2025
spa-raj
commented
- Blog post introducing Kubemodel - Opencost Data Model 2.0 which I worked on as part of my LFX Fall 2025 Mentorship.
Signed-off-by: Sparsh <[email protected]>
Signed-off-by: Sparsh <[email protected]>
✅ Deploy Preview for opencost ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ameijer
reviewed
Dec 4, 2025
Member
ameijer
left a comment
ameijer
left a comment
There was a problem hiding this comment.
general feedback - this is a tech blog post, I suggest you embed code snippets of a few selected data structures and walk the users through it. EMbed in places like the o(1) discussions etc
|
|
||
| ## The Challenge: Tracking Resources in a Dynamic Environment | ||
|
|
||
| Kubernetes is inherently dynamic. Pods come and go, deployments scale up and down, and resource names can be reused across recreation cycles. Traditional metric tracking that relies solely on resource names struggles in this environment: |
Member
There was a problem hiding this comment.
Suggested change
| Kubernetes is inherently dynamic. Pods come and go, deployments scale up and down, and resource names can be reused across recreation cycles. Traditional metric tracking that relies solely on resource names struggles in this environment: | |
| Kubernetes is inherently dynamic. Pods come and go, deployments scale up and down, and resource names can be reused across recreation cycles. Traditional metric tracking that relies solely on resource names struggles in this environment for a number of reasons including: |
|
|
||
| Kubernetes is inherently dynamic. Pods come and go, deployments scale up and down, and resource names can be reused across recreation cycles. Traditional metric tracking that relies solely on resource names struggles in this environment: | ||
|
|
||
| - **Name reuse**: When a pod is recreated with the same name, historical cost data can become ambiguous |
Member
There was a problem hiding this comment.
Suggested change
| - **Name reuse**: When a pod is recreated with the same name, historical cost data can become ambiguous | |
| - **Name reuse**: When a pod is recreated with the same name, historical cost data can become ambiguous. This is particularly problematic in stateful set pods |
| - **Owner/Controller** - Deployments, StatefulSets, ReplicaSets, DaemonSets, Jobs | ||
| - **Service** - Network service abstractions | ||
| - **Volume & PVC** - Persistent storage resources | ||
| - **ResourceQuota** - Namespace resource limits and requests |
|
|
||
| ## Binary Serialization with Bingen | ||
|
|
||
| KubeModel introduces **bingen-annotated Go structs** enabling efficient binary serialization. Bingen is IBM Kubecost's internal tool for generating binary serialization code from annotated Go structs. This provides: |
Member
There was a problem hiding this comment.
Suggested change
| KubeModel introduces **bingen-annotated Go structs** enabling efficient binary serialization. Bingen is IBM Kubecost's internal tool for generating binary serialization code from annotated Go structs. This provides: | |
| KubeModel introduces **bingen-annotated Go structs** enabling efficient binary serialization. Bingen is OpenCost specific tooling for generating binary serialization code from annotated Go structs. This provides: |
|
|
||
| These tests run across multiple time windows (1h, 6h, 24h) to ensure consistency and catch edge cases in real-world scenarios. | ||
|
|
||
| ## The Road Ahead |
Member
There was a problem hiding this comment.
this section feel very AI-ish. Nothing in here is regarding what you think the next steps are, just what has already been accomplished, right?
|
|
||
| ## Acknowledgments | ||
|
|
||
| A special thanks to my mentors for their guidance and support throughout this project: [Alex Meijer](https://github.com/ameijer), [Sean Holcomb](https://github.com/Sean-Holcomb), and [Niko Kovacevic](https://github.com/nikovacevic). No newline at end of file |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.