As of July 2024, we look to setup budget alerts for all cloud projects where we pay the bill from the cloud provider, independently if we pass through these costs or not to the community. We currently don’t look to setup budget alerts for communities paying their cloud provider bill directly.
This document describes how to enable (or opt-out of) budget alerts for a
cluster via the cluster’s associated terraform variables file (.tfvars).
AWS budget alerts are setup by default. To opt-out, declare:
default_budget_alert = {
"enabled" : false,
}First, ensure the following APIs are enable on the GCP project you’d like to enable budget alerting for:
Then edit the following variables in the relevant .tfvars file for the cluster.
Set
budget_alert_enabled = false, or delete the variable altogether (it is set totruein thevariables.tffile). This will ensure that the relevant resources will be created by terraform.Set
billing_account_id. This is the ID for the billing account linked to the project.You can find the ID by visiting the Billing console, ensuring the correct project is selected in the dropdown at the top. In the dialogue box, click “Go to Linked Billing Account”, and then click “Manage Billing Account” along the top. This will open a pane that gives you the Billing Account ID.
For accounts that we don’t manage, the process is the same but we may not have permission to view the Billing Account ID. In this case, we cannot enable budget alerting for this project.
With these variables set, you are ready to open a PR and perform a terraform apply!
To enable budget alerts for an Azure cluster, edit the following variables in the relevant .tfvars file for the cluster.
Set
budget_alert_enabled = trueThis will ensure that the relevant resources will be created by terraform.
Set
budget_alert_amountCurrent practice is to set this to the average expenditure of the last 3 months.
Then the alert will be triggered when the forecasted cost will exceed this value plus 20%.
You can find values to calculate that in the Cost analysis tab of the relevant Azure subscription:
Azure subscription->Cost Management->Cost analysis.If you are setting this up for a new cluster, you obviously don’t have this information yet! Instead, set the value to something like
500and we can adjust as the community begins to use it.With these variables set, you are ready to open a PR and perform a terraform apply!