AWS eks documentation change
Summary
Added documentation for Kubecost v3 including architectural changes (ClickHouse database, unified agent), performance improvements, upgrade instructions, and updated feature comparisons. Removed references to Kubecost v2 as the latest version.
Security assessment
The change documents 'secure messaging' for multi-cluster automation in Kubecost v3, which is a security feature. However, there's no evidence of addressing a specific vulnerability or incident. The removal of Prometheus dependency reduces attack surface but isn't explicitly framed as a security fix.
Diff
diff --git a/eks/latest/userguide/cost-monitoring-kubecost-bundles.md b/eks/latest/userguide/cost-monitoring-kubecost-bundles.md index 6e492ab16..0f1beffe6 100644 --- a//eks/latest/userguide/cost-monitoring-kubecost-bundles.md +++ b//eks/latest/userguide/cost-monitoring-kubecost-bundles.md @@ -5 +5 @@ -Kubecost v2Kubecost v1Frequently asked questionsAdditional Kubecost Features +Kubecost v3Kubecost v2Kubecost v1Frequently asked questionsAdditional Kubecost Features @@ -15 +15 @@ Amazon EKS provides an AWS optimized bundle of Kubecost for cluster cost visibil -This topic covers the available versions of Kubecost, and the differences between the available tiers. EKS supports Kubecost Version 1 and Version 2. Each version is available in different tiers. You can use _Amazon EKS optimized Kubecost bundle_ for your Amazon EKS clusters at no additional cost. You may be charged for use of associated AWS services, such as Amazon Managed Service for Prometheus. Also, you can use your existing AWS support agreements to obtain support. +This topic covers the available versions of Kubecost, and the differences between the available tiers. EKS supports Kubecost Version 1, Version 2, and Version 3. Each version is available in different tiers. You can use _Amazon EKS optimized Kubecost bundle_ for your Amazon EKS clusters at no additional cost. You may be charged for use of associated AWS services, such as Amazon Managed Service for Prometheus. Also, you can use your existing AWS support agreements to obtain support. @@ -17 +17 @@ This topic covers the available versions of Kubecost, and the differences betwee -As a Kubernetes platform administrator and finance leader, you can use Kubecost to visualize a breakdown of Amazon EKS charges, allocate costs, and charge back organizational units such as application teams. You can provide your internal teams and business units with transparent and accurate cost data based on their actual AWS bill. Moreover, you can also get customized recommendations for cost optimization based on their infrastructure environment and usage patterns within their clusters. For more information about Kubecost, see the [Kubecost](https://www.ibm.com/docs/en/kubecost/self-hosted/2.x) documentation. +As a Kubernetes platform administrator and finance leader, you can use Kubecost to visualize a breakdown of Amazon EKS charges, allocate costs, and charge back organizational units such as application teams. You can provide your internal teams and business units with transparent and accurate cost data based on their actual AWS bill. Moreover, you can also get customized recommendations for cost optimization based on their infrastructure environment and usage patterns within their clusters. For more information about Kubecost, see the [Kubecost](https://www.ibm.com/docs/en/kubecost/self-hosted/3.x) documentation. @@ -22,0 +23,41 @@ AWS and Kubecost collaborated to offer a customized version of Kubecost. This ve +## Kubecost v3 + +**What is the difference between Kubecost v2 and v3?** + +Kubecost 3.0 is a major architectural upgrade that delivers dramatically faster performance, enhanced scalability, and proactive optimization capabilities. The most significant change is the migration to a ClickHouse database, replacing DuckDB from version 2.8, which provides substantially faster queries and more reliable performance at scale. Kubecost 3.0 also introduces a unified agent that combines Kubecost and Cloudability functionality, eliminating the Prometheus dependency and reducing memory footprint while maintaining OpenCost compatibility. + +###### Important + +[Review the Kubecost documentation before upgrading to v3.](https://www.ibm.com/docs/en/kubecost/self-hosted/3.x) Migration from v2 requires careful planning and may impact report availability during transition. The Helm chart location has changed to `public.ecr.aws/kubecost/kubecost`. + +**Key architectural improvements in v3:** + + * **ClickHouse Database** : Replaces DuckDB for dramatically faster queries and better scalability + + * **Unified Agent** : Combines Kubecost and Cloudability functionality, eliminating Prometheus dependency + + * **Reduced Memory Footprint** : Substantially lower resource requirements while maintaining functionality + + * **Simplified Architecture** : Single-container pod topology for independent scaling and improved resiliency + + * **Enhanced Automation** : Automated Container Request Sizing with multi-cluster awareness and custom profiles + + + + +**Amazon EKS optimized bundle benefits in v3:** + +The _Amazon EKS optimized Kubecost bundle_ continues to be available at no additional charge and is exempt from the new $100,000 USD spend limit introduced in Kubecost v3 free tier. EKS users retain full access to all Kubernetes spend functionality regardless of spend levels. + +**Core features comparison:** + +Feature | Kubecost free tier 3.0 | Amazon EKS optimized Kubecost bundle 3.0 | Kubecost Enterprise 3.0 +---|---|---|--- +Cluster cost visibility | Unlimited clusters, gated at $100k USD spend over 30 days | Unified multi-cluster without spend limits when integrated with Amazon Managed Service for Prometheus | Unified and unlimited number of clusters across unlimited numbers of environments (i.e. multi-cloud) +Database backend | ClickHouse (local) | ClickHouse with Amazon Managed Service for Prometheus integration | ClickHouse with custom database options +Performance | Substantially faster queries vs v2 | Substantially faster queries vs v2 | Substantially faster queries vs v2 +Memory footprint | Reduced vs v2 (no Prometheus dependency) | Reduced vs v2 (no Prometheus dependency) | Reduced vs v2 (no Prometheus dependency) +Automated Container Request Sizing | Available (limited to 250 cores) | Available without core limits | Available without core limits +Spend limits | $100k USD over 30 days | No spend limits | No spend limits +Multi-cluster automation | Limited | Full multi-cluster awareness with secure messaging | Full multi-cluster awareness with secure messaging + @@ -159 +200,5 @@ Kubecost provides best effort to show cluster cost visibility for Amazon EKS on -You can upgrade your Kubecost version using standard Helm upgrade procedures. The latest versions are in the [Amazon ECR Public Gallery](https://gallery.ecr.aws/kubecost/cost-analyzer). +You can upgrade your Kubecost version using standard Helm upgrade procedures. For Kubecost v3, the latest versions are available at the new Helm chart location `public.ecr.aws/kubecost/kubecost`. Previous versions (v1 and v2) remain available in the [Amazon ECR Public Gallery](https://gallery.ecr.aws/kubecost/cost-analyzer). + +###### Important + +When upgrading to Kubecost v3, note that the Helm chart location has changed from `public.ecr.aws/kubecost/cost-analyzer` to `public.ecr.aws/kubecost/kubecost`. Update your Helm repository references accordingly. @@ -168,0 +214,12 @@ Kubecost provides a web dashboard that you can access through `kubectl` port for +**Does the new $100k spend limit in Kubecost v3 affect Amazon EKS users?** + +No. The $100,000 USD spend limit over 30 days introduced in Kubecost v3 free tier does not apply to _Amazon EKS optimized Kubecost bundle_ users. EKS users retain full access to all Kubernetes spend functionality regardless of spend levels. + +**What are the main performance improvements in Kubecost v3?** + +Kubecost v3 introduces substantial performance improvements through its ClickHouse database backend, which provides dramatically faster queries compared to the DuckDB used in v2.8. Additionally, the unified agent architecture eliminates the Prometheus dependency, reducing memory footprint while maintaining full functionality and OpenCost compatibility. + +**Can I upgrade directly from Kubecost v1 to v3?** + +No. Direct upgrade from v1 to v3 is not supported. You must first upgrade to v2, then migrate to v3. Review the Kubecost documentation for detailed migration guidance, as the process requires careful planning and may impact report availability during transition. + @@ -171 +228 @@ Kubecost provides a web dashboard that you can access through `kubectl` port for - * The following features are available in both Kubecost v1 and v2. + * The following features are available in Kubecost v1, v2, and v3. @@ -173 +230 @@ Kubecost provides a web dashboard that you can access through `kubectl` port for - * **Export cost metrics** – Amazon EKS optimized cost monitoring is deployed with Kubecost and Prometheus, which is an open-source monitoring system and time series database. Kubecost reads metric from Prometheus and then performs cost allocation calculations and writes the metrics back to Prometheus. The Kubecost front-end reads metrics from Prometheus and shows them on the Kubecost user interface. The architecture is illustrated in the following diagram. + * **Export cost metrics** – Amazon EKS optimized cost monitoring is deployed with Kubecost. In v1 and v2, Kubecost integrates with Prometheus for metrics storage and processing. In v3, Kubecost uses a ClickHouse database for dramatically improved performance while maintaining OpenCost compatibility. Kubecost reads metrics, performs cost allocation calculations, and provides data through its APIs and user interface. The architecture varies by version but maintains consistent functionality. @@ -177 +234 @@ Kubecost provides a web dashboard that you can access through `kubectl` port for -With [Prometheus](https://prometheus.io/) pre-installed, you can write queries to ingest Kubecost data into your current business intelligence system for further analysis. You can also use it as a data source for your current [Grafana](https://grafana.com/) dashboard to display Amazon EKS cluster costs that your internal teams are familiar with. To learn more about how to write Prometheus queries, see the [https://opencost.io/docs/installation/prometheus/](https://opencost.io/docs/installation/prometheus/) `readme` file on GitHub or use the example Grafana JSON models in the [Kubecost Github repository](https://github.com/kubecost/cost-analyzer-helm-chart/tree/develop/cost-analyzer) as references. +You can write queries to ingest Kubecost data into your current business intelligence system for further analysis. You can also use it as a data source for your current [Grafana](https://grafana.com/) dashboard to display Amazon EKS cluster costs that your internal teams are familiar with. To learn more about how to write queries, see the [OpenCost Configuration](https://opencost.io/docs/installation/prometheus/) documentation or use the example Grafana JSON models in the [Kubecost Github repository](https://github.com/kubecost/cost-analyzer-helm-chart/tree/develop/cost-analyzer) as references. @@ -179 +236 @@ With [Prometheus](https://prometheus.io/) pre-installed, you can write queries t - * **AWS Cost and Usage Report integration** – To perform cost allocation calculations for your Amazon EKS cluster, Kubecost retrieves the public pricing information of AWS services and AWS resources from the AWS Price List API. You can also integrate Kubecost with **AWS Cost and Usage Report** to enhance the accuracy of the pricing information specific to your AWS account. This information includes enterprise discount programs, reserved instance usage, savings plans, and spot usage. To learn more about how the AWS Cost and Usage Report integration works, see [AWS Cloud Billing Integration](https://www.ibm.com/docs/en/kubecost/self-hosted/2.x?topic=integrations-aws-cloud-billing-integration) in the Kubecost documentation. + * **AWS Cost and Usage Report integration** – To perform cost allocation calculations for your Amazon EKS cluster, Kubecost retrieves the public pricing information of AWS services and AWS resources from the AWS Price List API. You can also integrate Kubecost with **AWS Cost and Usage Report** to enhance the accuracy of the pricing information specific to your AWS account. This information includes enterprise discount programs, reserved instance usage, savings plans, and spot usage. To learn more about how the AWS Cost and Usage Report integration works, see [AWS Cloud Billing Integration](https://www.ibm.com/docs/en/kubecost/self-hosted/3.x?topic=integrations-aws-cloud-billing-integration) in the Kubecost documentation.