Important Updates

Kubecost recommends that any environment not using the Kubecost-provided Prometheus instance upgrade all clusters to Kubecost version 1.102+ due to a mismatched label that can cause container costs to be under-reported.

Additionally, Kubecost added a new recording rule in this version to enhance the CPU request-sizing recommendations accuracy when using the max algorithm. For clusters using existing Prometheus instances, this rule can be added by following this guide. Note that even without the recording rule, Kubecost will use a less efficient subquery in order to provide accurate recommendations.

Patch Release

• V1.102.1 fixes an issue that caused a panic where we incorrectly initialized certain data stores when ETL was disabled.