Skip to content

storage.md

Latest commit

 

History

History
20 lines (12 loc) · 1.49 KB

storage.md

File metadata and controls

20 lines (12 loc) · 1.49 KB

Cost Analyzer Persistent Volume

As of v1.67, Kubecost supports persisting its cache to disk. This dramatically reduces the load on startup against your Prometheus/Thanos installations on pod restart/redeploy, but commonly requires more storage.

If you are creating a new installation of kubecost:

We recommend that you back Kubecost with at least a 32GiB disk. This is the default as of 1.72.0

If you are upgrading an existing version of Kubecost

  • If your provisioner does supports volume expansion, we will automatically resize you to a 32GB disk in upgrade to 1.72.0
  • If your provisioner does not support volume expansion:
    • If all your configs are supplied via values.yaml in helm or via configmap and have not been added from the frontend, you can safely delete the PV and upgrade.
      • We suggest you delete the old PV, then run Kubecost with a 32GB disk. This is the default in 1.72.0
    • If you cannot safely delete the PV storing your configs and configure them on a new PV:
      • If you are not on a regional cluster, we recommend that you provision a second PV by setting persistentVolume.dbPVEnabled=true
      • If you are on a regional cluster, we recommend that you provision a second PV using a topology-aware storage class (more info). You can set this disk’s storage class by setting persistentVolume.dbStorageClass=your-topology-aware-storage-class-name