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

Cliff Colvin 6c88edde16 Merge pull request #2525 from opencost/AjayTripathy-fix-gpucost-2-cherrypick 2 年之前
.github cde609c0ab Fixed "OpenCost" 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 eba2989546 fix csv casing, precedence, add test 2 年之前
docs d4b47c5a75 change default allocation/compute aggregation to match allocation endpoint 2 年之前
kubernetes e0a310dcb0 (fix) added securityContext to the OpenCost backend container in the OpenCost deployment. Removed privileged escalation, dropped all capabilities, changed to read only access to file system and set the user to 1001 (same as Dockerfile) 3 年之前
pkg 5d8bf68de1 fix conflict 2 年之前
spec 637cd1c7a2 Minor formatting cleanups to make embedding in http://opencost.io/docs/specification a cleaner diff 2 年之前
test c765841355 fix float issues 2 年之前
tools 81eb9cfa29 feat(build): Add version and revision as labels 3 年之前
ui 9705cb2a85 Merge branch 'v1.106' into ui_fix_1.106 2 年之前
.dockerignore 93dcd24356 Docker Ignore 5 年之前
.gitignore 519c78fa72 Run builds locally before containerizing and add multi-arch support (#1941) 3 年之前
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 8469bd34fd Update code of conduct 3 年之前
CONTRIBUTING.md 519c78fa72 Run builds locally before containerizing and add multi-arch support (#1941) 3 年之前
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 bcaf863493 Clarifications and corrections 3 年之前
Makefile 301d63cf17 feat(metrics): Migrate to using existing version.go 3 年之前
NOTICE 0cad952152 Initial commit based off of Apache recommendations. 3 年之前
PROMETHEUS.md 7a7ee4b0dd Update PROMETHEUS.md 3 年之前
README.md d86b4f043a documentation addresses corrected 2 年之前
ROADMAP.md 45dd477d34 Roadmap refresh for March 2023 3 年之前
SECURITY.md d2b1076d31 Clarification that bug bounty not for previously disclosed publicly available CVEs 3 年之前
go.mod 97287dfda1 Update google.golang.org/grpc 2 年之前
go.sum 97287dfda1 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 onDemand 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, email at opencost@kubecost.com, or attend the biweekly OpenCost Working Group community meeting from the Community Calendar.

FAQ

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