Skip to main content
Kubernetes Budgeting
Updated over 2 months ago

Budget rules provide a means to set spending limits for your Kubernetes resources. You can create these rules effortlessly using the Budget feature. Budgets can be established for any Kubernetes group, such as namespaces, deployments, and clusters, or by labels like node and pod labels. Once you select the budget group, the budget values will be adjusted automatically based on your selection.

Creating a Budget

To get started, navigate to the Budget feature in the navigation bar and click the New budget button located in the top right corner.

Then a window will open with the option to create a new budget:

Create budget rules

  • Budget Name: Give your budget a name.

  • Select a month: Choose the time frame for your budget. You can only select one month at a time, but you'll be able to update it for the rest of the year after creating it.

  • Budget group: Select the relevant budget group (e.g., namespace, deployment, cluster) for your budget.

  • Value-Budget: Enter the budget for each value in the budget group.

  • Budget alerts: By default, alerts will be enabled to notify you when your forecasted costs exceed your set budget.

After entering all the necessary details, click the Create budget button to finalize your budget. Your budget rule will be created and added to the budget list.

Once your budget is created, a new window will appear displaying your budget details:

Editing a budget

In the new budget table, choose the relevant drill down to edit and press the edit button as shown in the screenshot below:

Manually add the budget for the rest of the year and click save.

Deleting a budget

To delete a budget, navigate to the budget main screen and click the Delete button next to the relevant budget.

This will open the Delete Budget window. Confirm the deletion by clicking the Delete button.

To learn more about budgets, please refer to our main documentation on this topic.

Still need help? Please feel free to reach out to our team at [email protected].

Did this answer your question?