Skip to content

πŸ“£ Announcement: kube-opex-analytics is becoming KubeLedger!Β #119

@rchakode

Description

@rchakode

TL;DR: We are renaming kube-opex-analytics to KubeLedger. This change reflects our evolution from a simple analytics program to a comprehensive accounting system for Kubernetes. We are also moving to a new GitHub organization: RealOps Labs.


❓ Why the change?

When this project started, the goal was simple: provide basic CPU and memory analytics for Kubernetes clusters. Over time, the tool has matured into a robust solution for usage accounting, cost allocation, and capacity planning, and for all kind of resources (currently: CPU, memory, **GPUv).

The name KubeLedger better represents what the tool does today: it acts as a system of record (ledger) for your cluster resources, providing accurate, long-term visibility into "who spent what".

πŸš€ What's New?

πŸ›  Migration Guide (For Existing Users)

Don't worry, the core logic remains the same. Here is how to update your setup:

  1. Update your Docker Image We are moving to the GitHub Container Registry (GHCR). Please update your manifests or Helm values:
image:
  repository: ghcr.io/realopslabs/kubeledger
  tag: v1.0.0 # Replace with the latest version

Note: We will continue to push updates to the old Docker Hub repository for a transition period of 6 months, but we strongly recommend switching to GHCR now.

  1. Update Environment Variables (Optional) We are introducing new KL_ prefixed environment variables to replace the old KOA_ ones. The old variables will continue to work for backward compatibility, but you will see a deprecation warning in the logs.

KOA_DB_LOCATION β†’ `KL_DB_LOCATIONv

KOA_BILLING_CURRENCY_SYMBOL β†’ KL_BILLING_CURRENCY_SYMBOL

(And so on...)

πŸ“… Timeline

Upcoming days/weeks: Repository transferred to realopslabs/kubeledger.

Upcoming days/weeks: New version released under the new name.

[Date + 6 Months]: Legacy Docker Hub images and KOA_ variables will be formally deprecated.

πŸ™ Thank You

Thank you to everyone who has starred, forked, and contributed to kube-opex-analytics. We are excited to continue this journey as KubeLedger!

If you have any questions or run into issues during the migration, please comment below.


The KubeLedger Team

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions