ring:infrastructure-cost-estimation

You can estimate cloud infrastructure costs by sizing workloads with tier-based options or a custom TPS value. The Skill reads Helm chart configurations to determine per-service resource needs and attributes costs across homolog and production environments for a profitability report.

Yes, you can calculate and compare infrastructure costs between homolog and production environments. The estimation process reads live Helm values to map autoscaling and resource sizing per environment, returning a comprehensive multi-environment profitability report.

Yes, cost estimation works by reading live Helm chart configurations from LerianStudio/helm. It extracts resource requests, limits, and autoscaling parameters directly from Helm values to validate inputs and calculate accurate per-service costs.

The best way to size infrastructure costs is by selecting a tier-based option or inputting a custom TPS value. This maps your workload sizing directly to environment costs and dispatches a calculator agent to produce detailed cost breakdowns.

To generate a profitability report, the Skill validates your Helm values and orchestrates a calculator agent to process the resource needs. It attributes the computed costs per environment and component, outputting detailed profitability insights.