Alex Meijer 6 месяцев назад
Родитель
Сommit
59fdcb5260
5 измененных файлов с 6 добавлено и 6 удалено
  1. 3 0
      MAINTAINERS.md
  2. 1 1
      NOTICE
  3. 1 1
      PROMETHEUS.md
  4. 1 0
      README.md
  5. 0 4
      SECURITY.md

+ 3 - 0
MAINTAINERS.md

@@ -3,6 +3,7 @@
 Official list of [OpenCost Maintainers](https://github.com/orgs/opencost/teams/opencost-maintainers). [OpenCost Committers](https://github.com/orgs/opencost/teams/opencost-committers) are granted Triage permissions for the OpenCost repositories. The [GOVERNANCE.md](https://github.com/opencost/opencost/blob/develop/GOVERNANCE.md) describes the process for becoming a committer and maintainer of the project.
 Official list of [OpenCost Maintainers](https://github.com/orgs/opencost/teams/opencost-maintainers). [OpenCost Committers](https://github.com/orgs/opencost/teams/opencost-committers) are granted Triage permissions for the OpenCost repositories. The [GOVERNANCE.md](https://github.com/opencost/opencost/blob/develop/GOVERNANCE.md) describes the process for becoming a committer and maintainer of the project.
 
 
 ## Maintainers
 ## Maintainers
+
 | Maintainer | GitHub ID | Affiliation | Email |
 | Maintainer | GitHub ID | Affiliation | Email |
 | --------------- | --------- | ----------- | ----------- |
 | --------------- | --------- | ----------- | ----------- |
 | Ajay Tripathy | @AjayTripathy | IBM | <ajay.tripathy@ibm.com> |
 | Ajay Tripathy | @AjayTripathy | IBM | <ajay.tripathy@ibm.com> |
@@ -11,8 +12,10 @@ Official list of [OpenCost Maintainers](https://github.com/orgs/opencost/teams/o
 | Matt Bolt | @​mbolt35 | IBM | <matthew.bolt@ibm.com> |
 | Matt Bolt | @​mbolt35 | IBM | <matthew.bolt@ibm.com> |
 | Niko Kovacevic | @nikovacevic | IBM | <Nicholas.Kovacevic@ibm.com> |
 | Niko Kovacevic | @nikovacevic | IBM | <Nicholas.Kovacevic@ibm.com> |
 | Sean Holcomb | @Sean-Holcomb | IBM | <sean.holcomb@ibm.com> |
 | Sean Holcomb | @Sean-Holcomb | IBM | <sean.holcomb@ibm.com> |
+| Warwick Peatey | @peatey | IBM | <warwick.peatey@ibm.com> |
 
 
 ## Opencost Emeritus Committers
 ## Opencost Emeritus Committers
+
 We would like to acknowledge previous committers and their huge contributions to our collective success:
 We would like to acknowledge previous committers and their huge contributions to our collective success:
 
 
 | Maintainer | GitHub ID | Affiliation | Email |
 | Maintainer | GitHub ID | Affiliation | Email |

+ 1 - 1
NOTICE

@@ -1,5 +1,5 @@
 OpenCost
 OpenCost
-Copyright 2022 - 2024 Cloud Native Computing Foundation
+Copyright 2022 - 2025 Cloud Native Computing Foundation
 
 
 This product includes software developed at
 This product includes software developed at
 The Cloud Native Computing Foundation (http://www.cncf.io).
 The Cloud Native Computing Foundation (http://www.cncf.io).

+ 1 - 1
PROMETHEUS.md

@@ -1 +1 @@
-Available at <https://www.opencost.io/docs/installation/prometheus>
+Available at <https://www.opencost.io/docs/installation/prometheus>

+ 1 - 0
README.md

@@ -24,6 +24,7 @@ To see the full functionality of OpenCost you can view [OpenCost features](https
 - Allocation for in-cluster K8s resources like CPU, GPU, memory, and persistent volumes
 - Allocation for in-cluster K8s resources like CPU, GPU, memory, and persistent volumes
 - Easily export pricing data to Prometheus with /metrics endpoint ([learn more](https://www.opencost.io/docs/installation/prometheus))
 - Easily export pricing data to Prometheus with /metrics endpoint ([learn more](https://www.opencost.io/docs/installation/prometheus))
 - Carbon costs for cloud resources
 - Carbon costs for cloud resources
+- MCP support
 - Support for external costs like Datadog through [OpenCost Plugins](https://github.com/opencost/opencost-plugins)
 - Support for external costs like Datadog through [OpenCost Plugins](https://github.com/opencost/opencost-plugins)
 - Free and open source distribution ([Apache2 license](LICENSE))
 - Free and open source distribution ([Apache2 license](LICENSE))
 
 

+ 0 - 4
SECURITY.md

@@ -20,10 +20,6 @@ For example, if `v1.102.0` is the most recent stable version, we will address se
 
 
 The OpenCost project has enabled [Private vulnerability reporting](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability) for our repositories which allows for direct reporting of issues to administrators and maintainers in a secure fashion. Please include a thorough description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. The team will help diagnose the severity of the issue and determine how to address the issue. Issues deemed to be non-critical will be filed as GitHub issues. Critical issues will receive immediate attention and be fixed as quickly as possible.
 The OpenCost project has enabled [Private vulnerability reporting](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability) for our repositories which allows for direct reporting of issues to administrators and maintainers in a secure fashion. Please include a thorough description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. The team will help diagnose the severity of the issue and determine how to address the issue. Issues deemed to be non-critical will be filed as GitHub issues. Critical issues will receive immediate attention and be fixed as quickly as possible.
 
 
-### Kubecost Bug Bounty
-
-Kubecost offers a Bug Bounty program that pays $250 USD for unique, not previously disclosed publicly available CVEs, and accepted security bug reports submitted to vulnerability-report@kubecost.com.
-
 ## Disclosure policy
 ## Disclosure policy
 
 
 For known public security vulnerabilities, we will disclose the disclosure as soon as possible after receiving the report. Vulnerabilities discovered for the first time will be disclosed in accordance with the following process:
 For known public security vulnerabilities, we will disclose the disclosure as soon as possible after receiving the report. Vulnerabilities discovered for the first time will be disclosed in accordance with the following process: