Metering Operator Versions Save

Metering 0.8.0 is mostly an internal release to snapshot the current state of metering in preparation of upcoming breaking changes.

Since 0.7.0:

• Refactored internal handling of resources.
  • Reduces amount of unnecessary work doing no-ops and as a result also reduces logging verbosity
  • Improves responsiveness by requeuing resources when their dependent resources have changed
• Moves all status related information such as table names, view name fields into a status field on CRs rather than having them be top-level fields.
• Documented the current release process
• Added Prometheus instrumentation on HTTP API operations
• Fixed a bug preventing the log-level configuration from taking effect
• Changed default log level to info
• Replace CHARGEBACK_ environment variable prefix with REPORTING_OPERATOR_
• Support configuring alternative Prometheus endpoint URL at a ReportDataSource level

In preparation of building OCP images:

• Refactor helm operator image to use a new quay.io/coreos/helm base image rather than building helm
• Refactor presto image to use a new quay.io/coreos/presto base image rather downloading Presto releases
• Updates the reporting-operator and metering-helm-operator images to each include the minimum to build each image and no longer the metering-builder image

This is the first public release of Operator Metering (previously known as kube-chargeback).

Operator Metering (metering for short) is designed to run inside Kubernetes and collect metrics from Prometheus periodically, storing them for long-term analysis.

Operator Metering extends the Kubernetes API by providing new Custom Resources like Reports and ScheduledReports for reporting on usage, or other custom metrics.

Documentation for this release can be found on the release-0.6 branch.

Please file issues if you run into any problems.

• Full Support for AWS Billing Correlation Reports
• Configurable using Helm Operator
• Improved documentation
• More tests