# Pod disruption budget

> [HTML Version](pod-disruption-budget.html)

You can protect services from sudden disconnection. To do this, use the **Pod Disruption Budget** tool. It allows you to control how many pods can be disconnected at a time during scheduled maintenance, such as node upgrades or migrations.

## How to configure the podDisruptionBudget parameter 

The \[OBJECT\] parameter can be configured in the \[OBJECT\] file. Navigate to the \[OBJECT\] field and set the values, for example:

````
global:  
  podDisruptionBudget:  
    enabled: true  
    minAvailable: 2  
    # maxUnavailable: 1

````
Where:

- \[OBJECT\]. The \[OBJECT\] value enables the parameter.

- \[OBJECT\] is the minimum number of pods that must remain operational and available during scheduled operations.

- \[OBJECT\] is the maximum number of pods that are unavailable during scheduled operations.

Once the parameter is configured, apply it as described in the [Modify BRIX parameters article](change-settings-enterprise.md#apply-new-parameters).

## Default values for the podDisruptionBudget parameter

By default, the\[OBJECT\] parameter is disabled. If you set \[OBJECT\] to \[OBJECT\] but do not specify a value for \[OBJECT\] or \[OBJECT\], the following settings apply:

````
spec:  
  minAvailable: 1

````