How the Integration Works
Vantage looks at pod lifecycle data and the underlying nodes that pods run on. By joining the lifecycle data of each pod (along with the greater of either the reserved or actual CPU/memory prescribed) with the specific rate information of the underlying node, Vantage allocates subcategories of the node (vCPU, memory, GPU, storage, etc.) to the pod. The lifecycle of the EC2 instance is also automatically determined (On-Demand, Spot, Reserved, Savings Plans, EDP, etc.). This allows you to see costs by the following dimensions:- By container name
- By Kubernetes service
- By Kubernetes namespace
- By Kubernetes label
Enable Kubernetes Costs
You must have a Vantage Organization Owner or Integration Owner role to add or remove this integration. See the Role-Based Access Control documentation for details.
Manage Workspace Access
Once the import is complete and the integration status changes to Stable, you can select which workspaces this integration is associated with. See the Workspaces documentation for information.Data Refresh
See the provider data refresh documentation for information on when data for each provider refreshes in Vantage.Reporting Dimensions
On Kubernetes Cost Reports, you can filter across several dimensions:- Account (associated account name)
- Tag (includes Kubernetes grouping names and values, for example, namespace, and virtual tags created in Vantage for this provider)
- Region (e.g., Westus2)
- Charge Type (e.g., Usage)
- Cluster (cluster name)