Sections in this category

Federated Clusters

To view data from multiple clusters simultaneously, Kubecost cluster federation must be enabled. This document walks through the necessary steps for enabling this feature.

Note: This feature today requires an Enterprise license.

Master cluster (Postgres)

  1. Follow steps here to enable long-term storage.
  2. Ensure remoteWrite.postgres.installLocal is set to true in values.yaml
  3. Provide a unique identifier for your cluster in
  4. Create a service definition to make Postgres accessible by your other clusters. Below is a sample service definition.
    Warning: this specific service definition may expose your database externally with just basic auth protecting. Be sure the follow the necessary guidelines of your organization.
apiVersion: v1
kind: Service
    app: cost-analyzer kubecost cost-analyzer
  name: pgprometheus-remote
  namespace: kubecost
  - name: server
    port: 5432
    protocol: TCP
    targetPort: 5432
    app: postgres
  type: LoadBalancer
  1. Helm upgrade with the new values.

Secondary clusters (Postgres)

Following these steps for clusters that send data to the master cluster:

  1. Same as you did for the master, follow steps here to enable long-term storage.
  2. Set remoteWrite.postgres.installLocal to false in values.yaml so you do not redeploy Postgres in this cluster.
  3. Set to any unique identifier of your cluster, e.g. dev-cluster-7.
  4. Set prometheus.remoteWrite.postgres.remotePostgresAddress to the externally accessible IP from master cluster.
  5. Ensure postgres.auth.password is updated to reflect the value set at the master.
  6. Helm upgrade with the new values.

Verification of Postgres multi-cluster

Connect to the master cluster and complete the folllowing:

Visit this endpoint http://<master-kubecost-address>/model/costDataModelRangeLarge

Here’s an example use: http://localhost:9090/model/costDataModelRangeLarge

You should see data with both cluster_id values in this response.

Federated Clusters (Thanos)

  1. Follow steps here to enable Thanos durable storage on a Master cluster.

  2. Repeat the process in Step 1 for each additional secondary cluster, with the following Thanos recommendations:

    • Reuse your existing storage bucket and access credentials.
    • Do not deploy multiple instances of thanos-compact.
    • Optionally deploy thanos-bucket in each additional cluster, but it is not required.
    • Optionally disable and thanos.query (Clusters with store/query disabled will only have access to their metrics but will still write to the global bucket.)

Thanos modules can be disabled in thanos/values.yaml, or in values-thanos.yaml if overriding these values from a values-thanos.yaml file supplied from command line (helm upgrade kubecost -f values.yaml -f values-thanos.yaml), or by passing these parameters directly via helm install or upgrade as follows:

  --set thanos.compact.enabled=false --set thanos.bucket.enabled=false

You can also optionally disable, thanos.query and thanos.queryFrontend with thanos/values.yaml or with these flags:

  --set thanos.query.enabled=false --set --set thanos.queryFrontend.enabled=false
  1. Ensure you provide a unique identifier for to have additional clusters be visible in the Kubecost product, e.g. cluster-two.

  2. Follow the same verification steps available here.

Edit this doc on Github