Pod disruption budget

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 podDisruptionBudget parameter can be configured in the values-elma365.yaml file. Navigate to the .Values.global.podDisruptionBudget field and set the values, for example:

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

Where:

• enabled. The true value enables the parameter.
• minAvailable is the minimum number of pods that must remain operational and available during scheduled operations.
• maxUnavailable 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 Enterprise parameters article.

Default values for the podDisruptionBudget parameter

By default, thepodDisruptionBudget parameter is disabled. If you set .Values.global.global.podDisruptionBudget.enabled to true but do not specify a value for minAvailable or maxUnavailable, the following settings apply:

spec:
 minAvailable: 1

Was this helpful?

Thanks for your feedback!

Please specify why:

Recommendations did not help meArticle is hard to understandDidn’t answer my questionContent does not match the topicOther

How can we improve the article?

YesNo

Please specify whyRecommendations did not help meArticle is hard to understandDidn’t answer my questionContent does not match the topicOther