Skip to content

federated-clusters.md

Latest commit

 

History

History
70 lines (52 loc) · 3.2 KB

federated-clusters.md

File metadata and controls

70 lines (52 loc) · 3.2 KB

To view data from multipe clusters simultaneously, Kubecost cluster federation must be enabled. This documents 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 prometheus.server.global.exernal_labels.cluster_id
  4. Create a service definition to make Postgres accessible by your other clusters. Below is a sample service definition. Warning: this specific service defition may expose your database externally with just basic auth protecting. Be sure the follow the necessary guidelines of your organiztion.
apiVersion: v1
kind: Service
metadata:
  labels:
    app: cost-analyzer
    app.kubernetes.io/instance: kubecost
    app.kubernetes.io/name: cost-analyzer
  name: pgprometheus-remote
  namespace: kubecost
spec:
  ports:
  - name: server
    port: 5432
    protocol: TCP
    targetPort: 5432
  selector:
    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 prometheus.server.global.exernal_labels.cluster_id 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:

Vist 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. Complete the process in Step 1 for each additional cluster by reusing your existing storage bucket and access credentials. Note: it is not necessary to deploy another instance of thanos-compact or thanos-bucket in each additional cluster. These are optional, but they can easily be disabled in thanos/values.yaml or by passing these parameters directly via helm install or upgrade as follows:

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

  1. Ensure you provide a unique identifier for prometheus.server.global.exernal_labels.cluster_id to have additional clusters be visible in the Kubecost product, e.g. cluster-two.

  2. Follow the same verification steps available here.