The Hybrid Data Pipeline Helm chart provides support for Pod Disruption Budgets across Kubernetes resources. This capability protects application availability during voluntary disruptions such as planned maintenance, node upgrades, and cluster scaling.

Pod Disruption Budgets limit the number of pods that can be down simultaneously during maintenance events. They ensure that your Hybrid Data Pipeline service remains available even while the cluster infrastructure is being updated.

By default, Pod Disruption Budget configuration varies by component. You can customize these settings in the values.yaml file based on their availability requirements.

Pod Disruption Budgets can be configured in the values.yaml file for the following resources:

  • Hybrid Data Pipeline server pods
    
  hdp:
    pdb:
      create: true
      minAvailable: "1"
  • PostgreSQL system database primary instance
    
  postgresql:
    primary:
      pdb:
        create: true
        minAvailable: 1
  • PostgreSQL system database replica instances
    
  postgresql:
    readReplicas:
      pdb:
        create: true
        maxUnavailable: 1
Note: Pod Disruption Budgets are only effective when you have more than one replica. In addition, you must use either minAvailable or maxUnavailable. You may not use both these parameters in a one configuration.

For descriptions of supported parameters, see Helm chart parameters or refer to the values.yaml file in the Hybrid Data Pipeline Helm chart GitHub repository.