Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: add ablity to specify the TopologySpreadConstraint #147

Open
huwmjenkins opened this issue Aug 16, 2024 · 0 comments · May be fixed by #148
Open

[Feature]: add ablity to specify the TopologySpreadConstraint #147

huwmjenkins opened this issue Aug 16, 2024 · 0 comments · May be fixed by #148

Comments

@huwmjenkins
Copy link

Feature Description

Topology spread constraints can be used to control how Pods are spread across a cluster among failure-domains such as regions, zones, nodes, and other user-defined topology domains. This can help to achieve high availability as well as efficient resource utilization. For Solace, running in a cloud based environment means each node can be run in a different availability zone.

Use Case

This would be used to ensure that all three nodes of a high availability solace deployed to a cloud environment was spread evenly across multiple availability zones.

Proposed Solution

In the same way that tolerations and affinity were added to the helm chart the topologySpreadConstraints just needs to be added to the values.yaml and the solaceStatefulSet.yaml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant