Add ability to configure a pod topology spread constraint #37
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.
This adds the ability to specify a pod topology spread constraint. This is the newer way of making sure a deployment won't run on the same node or in the same AZ as another pod, but by using a maxSkew instead of just an affinity.
This helps newer scaling tools, like Karpenter, add node where they're needed based on this maxSkew and the constraints.
Make it configurable by env variables on the egress operator deployment - ideally in the future we'd expand the CRD to specify this in the external service (or set sensible defaults)