feat(helm): possibility to set pod disruption budget

[kostiantyn-nemchenko]

What

Allow configuring a pod disruption budget to control how many instances can be down simultaneously for a short period due to voluntary disruption such as Kubernetes node or system software upgrade.

How

Added helm manifests for creating a PodDisruptionBudget object per each component that could have more than one replica.

Recommended reading order

1. charts/airbyte/values.yaml
2. charts/airbyte/values.yaml.test
3. charts/airbyte-connector-builder-server/values.yaml
4. charts/airbyte-cron/values.yaml
5. charts/airbyte-metrics/values.yaml
6. charts/airbyte-server/values.yaml
7. charts/airbyte-temporal/values.yaml
8. charts/airbyte-webapp/values.yaml
9. charts/airbyte-worker/values.yaml
10. charts/airbyte-connector-builder-server/templates/pdb.yaml
11. charts/airbyte-cron/templates/pdb.yaml
12. charts/airbyte-metrics/templates/pdb.yaml
13. charts/airbyte-server/templates/pdb.yaml
14. charts/airbyte-temporal/templates/pdb.yaml
15. charts/airbyte-webapp/templates/pdb.yaml
16. charts/airbyte-worker/templates/pdb.yaml

Can this PR be safely reverted / rolled back?

• [X] YES 💚
• [ ] NO ❌

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

:x: kostiantyn-nemchenko
:x: perangel
_{You have signed the CLA already but the status is still pending? Let us recheck it.}