Release Notes

TOC

4.1.6

Features and Enhancements

Supports Alauda Container Platform 4.2.0 version

Known Issues

  • When a StatefulSet's Pod is stopped and then restarted, the platform takes the earliest runtime of the Pod's daily operation as the start time and the latest runtime as the end time, ignoring any intermediate periods when it was not running. This results in the Pod being metered for more time than its actual operational hours.

4.1.0

Features and Enhancements

  1. Tenant-Level Metering and Billing
  • Introduced expense statistics and detailed expense reports from a project perspective.
  • Project administrators can now view expenses related to their specific projects.
  1. Usage Statistics
  • Both the platform-level and project-level expense statistics pages now support viewing usage statistics.
  1. Billing Model Management
  • Abstracted various billing items and billing methods into billing models to support universal metering and billing.
  • Previously, CPU, memory, and storage rates could only be set in the plugin configuration with a single billing method.
  • Now, billing models allow management of billing resources, billing methods, and unit prices for each cluster.
  • After plugin installation, there will be no default billing; administrators need to plan and configure billing models and associate them with clusters needing billing.
  • Billing models support multiple billing resources and methods.
  • Differential pricing can be set using resource tags (e.g., different prices for different GPU models).
  1. Universal Metering and Billing Solution
  • Provided a hot-pluggable universal metering and billing solution based on billing models, eliminating the need for product releases.
  • Customizable for various products/customers.
  • Requires collection and storage of billing-related metrics in the monitoring system.
  • Users must define the billing items and methods for their required resources.
  • PromQL definitions are needed for the billing items and methods used.

Known Issues

  • When a StatefulSet's Pod is stopped and then restarted, the platform takes the earliest runtime of the Pod's daily operation as the start time and the latest runtime as the end time, ignoring any intermediate periods when it was not running. This results in the Pod being metered for more time than its actual operational hours.