add topologySpreadConstraints to deployment #138
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for this great helm chart to get netbox up and running on Kubernetes. I'm currently standing up my own deployment and was trying to spread the web workers across availability zones in AWS. I noticed that the chart doesn't support topologySpreadConstraints yet, so I figured I would add it. At the moment I'm using Kustomize to add the constraint after the helm render inside of ArgoCD.
I'm happy to make any modifications necessary.