In order to gather the data we need to perform allocation for a given cluster, you will need to deploy the Cloudability Metrics Agent to each cluster you want to report on. This is done through a YAML deployment provisioned for each cluster, and dependent on the specific Kubernetes version you are running.
Simply click the yellow plus icon (see below), and fill out the form with your Cluster Name and Kubernetes version. We will generate a YAML file for you to download, and you can run the deployment from there. Once complete, we will start receiving data for the cluster within a few hours. Data for that cluster should show up in the app the following day. If you run into any issues with the deployment, please contact support.
Please do not use the same YAML file for more than one cluster. Each Cluster gets a unique key and requires a new deployment template. Re-use of the unique key may result in sub-optimal performance.
Re-Provisioning or Upgrading Clusters
When upgrading to a new Kubernetes version, or re-provisioning an existing cluster, you may need to install a new version of the Cloudability Metrics Agent to ensure data continues to flow for that cluster. To do so, fill out the provisioning form in Cloudability with the same cluster name and new Kubernetes version, and you'll get a YAML file for the deployment. This is particularly important when upgrading to a new Kubernetes Version. Please contact support with any questions about upgrades.
GKE Specific Instructions
Please add a cluster label in each cluster with key: gke-cluster and value: the cluster name(s) you set in the form/YAML. This will allow us to map GKE clusters to line items in the GCP billing file, and allocate costs to your clusters.
Cloudability will need to ingest a billing file with the cluster labels you added, which can take up to 48 hours. Once we have processed the new billing file, you will need to create a new tag mapping in the Cloudability application. Set a Cloudability Dimension as: gke-cluster, and map this to the gke-cluster tag. This is a one time need, not per cluster.
Ensure that your account has cluster-admin to your account before deploying the Metrics Agent. By default, a user account does not have the cluster-admin role. Use the following command on the GKE cluster to grant a user the cluster-admin role: "kubectl create clusterrolebinding username-cluster-admin-binding --clusterrole=cluster-admin --firstname.lastname@example.org"