Kubecost provides real-time cost visibility and insights for your Kubernetes clusters. This guide shows you how to deploy Kubecost on your Qovery cluster to track and optimize your infrastructure spending.Documentation Index
Fetch the complete documentation index at: https://qovery-update-kubecost-tuto.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites: You need a functioning Qovery cluster before starting this tutorial.
This tutorial takes approximately 5 minutes to complete.
Installation
This tutorial is based on a specific version of Kubecost. We have created it to assist our users, but Qovery is not responsible for any configuration issues — please contact Kubecost support for chart-specific questions.
Step 1: Add the Kubecost Helm Repository
Add Helm Repository
In Qovery Console:
- Go to Settings → Helm Repositories
- Click Add Repository
- Configure:
- Repository name:
Kubecost - Kind:
HTTPS - Repository URL:
https://kubecost.github.io/kubecost
- Repository name:
Step 2: Create the Kubecost Helm Service
Create Helm Service
In your environment:
- Click Create → Helm Chart
- Configure:
- Application name:
kubecost - Helm source:
Helm repository - Repository:
Kubecost - Chart name:
kubecost - Version:
3.1.8(or latest from Kubecost) - Allow cluster-wide resources: ✔️
- Application name:
Step 3: Store Secrets and Variables
Add optional variables
Open the Kubecost service overview and go to the Variables section.Add these variables as needed:
See Environment Variables for more details on managing variables in Qovery.
| Variable | Value | Scope | Secret | Notes |
|---|---|---|---|---|
KUBECOST_TOKEN | <your_token> | Service | ✔️ | Optional — required for Kubecost Business/Enterprise features |
Step 4: Configure Values Override
In the Override as file section of your Helm service, add the following configuration:How
qovery.env.* works: At deploy time, Qovery replaces qovery.env.KUBECOST_TOKEN with the actual value of the KUBECOST_TOKEN variable. The real value never appears in the Qovery UI — it is only injected at Helm install time. See Environment Variables in Helm Values for more details.Step 5: Deploy the Chart
Step 6: Access Kubecost via Port Forward
Instead of exposing Kubecost publicly, usekubectl port-forward to access the dashboard securely from your local machine.
Connect to your cluster
Download your cluster’s kubeconfig from the Qovery Console:Verify the connection:See Cluster Kubeconfig for more details.
- Go to Organization → Clusters
- Click on your cluster
- Open the Actions menu and select Get Kubeconfig
kubectl to use it:Get your environment namespace
In Qovery Console, go to your environment and find the Kubernetes namespace in the environment details. It follows the pattern
z<env-id-prefix>-<env-name>.Alternatively, list namespaces on your cluster:Find the Kubecost service name
List services in your namespace to find the Kubecost dashboard service:
Forward the Kubecost port
Run the following command, replacing Then open your browser at http://localhost:9090.
<namespace> and <service-name> with the values from the previous steps:Conclusion
You’ve successfully deployed Kubecost on your Qovery cluster. You can now access the Kubecost dashboard to monitor your Kubernetes costs and get optimization recommendations. To learn more about using Kubecost, check out their Getting Started guide.Next Steps
Kubecost Documentation
Learn more about Kubecost features
Optimize
Optimization strategies with Qovery
Qovery Observe
Built-in observability
Datadog
Advanced monitoring with Datadog