Cross-cloud cost allocation models for Kubernetes workloads https://kubecost.com

Cliff Colvin c998955378 Merge pull request #2370 from cliffcolvin/107-sanitize-labels 2 年 前
.github ba43c5355e Update stale.yml 2 年 前
.idea 93fbec52fb add intellij and goland gofmt settings to be consistent with vscode 3 年 前
cmd c7706a4fb2 Renamed Kubecost Github reference to OpenCost 3 年 前
config dad87d9821 broken state 3 年 前
configs 5afddd6b81 Sets projectID and billingDataDataset to empty strings. (#2122) 2 年 前
docs d4b47c5a75 change default allocation/compute aggregation to match allocation endpoint 2 年 前
kubernetes f4909d3027 Switch back to `latest` tag for UI 2 年 前
pkg 329fe69427 sanitize asset labels 2 年 前
spec 637cd1c7a2 Minor formatting cleanups to make embedding in http://opencost.io/docs/specification a cleaner diff 2 年 前
test 42976a2b8b GTM-52 Fix parsing of GCP pricing and create new node diagnostic pricing API 2 年 前
tools 81eb9cfa29 feat(build): Add version and revision as labels 3 年 前
ui 25039598e8 Sync Dockerfile and Dockerfile.cross and run as non-root user 2 年 前
.dockerignore 93dcd24356 Docker Ignore 5 年 前
.gitignore 0f9c2ceecf fix empty launch config .vscode and add to the .gitignore for future issue (#2191) 2 年 前
ADOPTERS.MD d7a2cc1280 Updating to use the [definitions provided by the CNCF](https://github.com/cncf/toc/blob/main/FAQ.md#what-is-the-definition-of-an-adopter). 3 年 前
CODE_OF_CONDUCT.md 8241f30690 Direct inquiries to Slack and the community meetings rather than Kubecost 2 年 前
CONTRIBUTING.md 5e7903e33c Update CONTRIBUTING.md 2 年 前
Dockerfile 1421dbf485 Ensure permissions on copied files are world-readable. 3 年 前
Dockerfile.cross 519c78fa72 Run builds locally before containerizing and add multi-arch support (#1941) 3 年 前
GOVERNANCE.md bcaf863493 Clarifications and corrections 3 年 前
LICENSE e21bf66dc1 Add LICENSE 7 年 前
MAINTAINERS.md 4296d4c0fb Merge branch 'develop' into maintainers 2 年 前
Makefile 301d63cf17 feat(metrics): Migrate to using existing version.go 3 年 前
NOTICE 0cad952152 Initial commit based off of Apache recommendations. 3 年 前
PROMETHEUS.md 6434740792 Updated URLs after opencost.io/docs/ rearrangement. 2 年 前
README.md 526e6ec039 Update README.md 2 年 前
ROADMAP.md 8241f30690 Direct inquiries to Slack and the community meetings rather than Kubecost 2 年 前
SECURITY.md d2b1076d31 Clarification that bug bounty not for previously disclosed publicly available CVEs 3 年 前
go.mod e271d1ed90 Update google.golang.org/grpc 2 年 前
go.sum e271d1ed90 Update google.golang.org/grpc 2 年 前
justfile 519c78fa72 Run builds locally before containerizing and add multi-arch support (#1941) 3 年 前
opencost-header.png c9a4dff062 opencost readme 4 年 前

README.md

OpenCost — your favorite open source cost monitoring tool for Kubernetes

OpenCost models give teams visibility into current and historical Kubernetes spend and resource allocation. These models provide cost transparency in Kubernetes environments that support multiple applications, teams, departments, etc.

OpenCost was originally developed and open sourced by Kubecost. This project combines a specification as well as a Golang implementation of these detailed requirements.

OpenCost allocation UI

To see the full functionality of OpenCost you can view OpenCost features. Here is a summary of features enabled:

  • Real-time cost allocation by Kubernetes cluster, node, namespace, controller kind, controller, service, or pod
  • Dynamic on-demand asset pricing enabled by integrations with AWS, Azure, and GCP billing APIs
  • Supports on-prem k8s clusters with custom CSV pricing
  • Allocation for in-cluster resources like CPU, GPU, memory, and persistent volumes.
  • Easily export pricing data to Prometheus with /metrics endpoint (learn more)
  • Free and open source distribution (Apache2 license)

Getting Started

You can deploy OpenCost on any Kubernetes 1.8+ cluster in a matter of minutes, if not seconds!

Visit the full documentation for recommended install options.

Usage

Contributing

We :heart: pull requests! See CONTRIBUTING.md for information on building the project from source and contributing changes.

Community

If you need any support or have any questions on contributing to the project, you can reach us on CNCF Slack in the #opencost channel or attend the biweekly OpenCost Working Group community meeting from the Community Calendar to discuss OpenCost development.

FAQ

You can view OpenCost documentation for a list of commonly asked questions.