Installing in Air-gapped Environments
This doc is the primary reference for installing Kubecost in an air-gapped environment.
The following images will need to be downloaded. Please substitute the appropriate version for prod-x.xx.x. Latest releases can be found here.
- Frontend: gcr.io/kubecost1/frontend:prod-x.xx.x
- CostModel: gcr.io/kubecost1/cost-model:prod-x.xx.x
- BusyBox: registry.hub.docker.com/library/busybox:latest (only for NFS)
- Cluster controller: gcr.io/kubecost1/cluster-controller:v0.9.0 (used for write actions)
- Grafana Dashboards: grafana/grafana:9.4.7
- kiwigrid/k8s-sidecar:1.23.1 (optional if not using Grafana sidecar)
There are two options to configure asset prices in your on-premise Kubernetes environment:
- Simple pipeline: per resource prices can be configured in a Helm values file (reference) or directly in the Kubecost Settings page. This allows you to directly supply the cost of a CPU month, RAM Gb month, etc.
Use quotes if setting "0.00" for any item under
kubecostProductConfigs.defaultModelPricing. Failure to do so will result in the value(s) not being written to the Kubecost cost-model's PV (/var/configs/default.json).
When setting CPU and RAM monthly prices, the values will be broken down to the hourly rate for the total monthly price set under kubecost.ProductConfigs.defaultModelPricing. The values will adjust accordingly in /var/configs/default.json in the kubecost cost-model container.
* _Advanced pipeline:_ this method allows each individual asset in your environment to have a unique price. This leverages the Kubecost custom CSV pipeline which is available on Enterprise plans.
- Use a proxy for the AWS pricing API. You can set
extra env varto the address of your proxy.