Add Support for topologySpreadConstraints in Zeebe Helm Charts to Ensure Multi-AZ Pod Distribution

[ManuelDittmar]

Describe the use case:

In our deployment of Zeebe, it is crucial to ensure high availability and fault tolerance. Our infrastructure spans multiple Availability Zones (AZs) to minimize the risk of downtime due to a single point of failure. By having Zeebe pods spread across multiple AZs, we can ensure that the failure of an entire AZ will not affect the overall availability and reliability of our Zeebe deployment. This setup is essential for maintaining continuous business operations and achieving our service level agreements (SLAs).

Describe the enhancement/feature:

We propose an enhancement to the Zeebe Helm charts that allows the configuration of topologySpreadConstraints. This feature will enable us to specify constraints ensuring that Zeebe pods are evenly distributed across multiple AZs.

Desired outcome and acceptance tests:

Zeebe pods are evenly distributed across all available AZs, ensuring that no single AZ failure can cause a complete service outage.

[aabouzaid]

@ManuelDittmar, just to ensure that this request is for Multi-Availability Zones and is not related to Multi-region, right?

[ManuelDittmar]

@aabouzaid yes exactly :)