Add topologySpreadConstraints support + pin to 1.1.341 (CE-271)#8
Merged
Eric Hibbs (flowstate) merged 3 commits intoJun 30, 2026
Conversation
Expose a `topologySpreadConstraints` pod-spec value (default empty, opt-in) so operators can evenly distribute replicas across zones/nodes, instead of relying on soft pod anti-affinity. Bumps chart to 0.5.0 and documents a zone-spread example in the README. Requested by Vercel. Closes CE-271. Co-authored-by: Cursor <cursoragent@cursor.com>
Eric Hibbs (flowstate)
added a commit
that referenced
this pull request
Jun 24, 2026
Bump appVersion + image.tag 1.1.337 -> 1.1.341 (current latest on Docker Hub) and chart version 0.4.2 -> 0.5.1 so it sequences cleanly after the 0.5.0 topologySpreadConstraints change (PR #8). Co-authored-by: Cursor <cursoragent@cursor.com>
2 tasks
Fold the version pin into this PR: appVersion + image.tag -> 1.1.341 (current latest on Docker Hub). Chart stays at 0.5.0 so the feature and the pin ship as a single release. Co-authored-by: Cursor <cursoragent@cursor.com>
Eric Hibbs (flowstate)
changed the title
4 tasks
…topologyspreadconstraints-support-to-socket-firewall Co-authored-by: Cursor <cursoragent@cursor.com> # Conflicts: # helm/Chart.yaml # helm/values.yaml
Phil Gran (philgran)
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
topologySpreadConstraintspod-spec value (default[], opt-in) to the Socket Firewall Helm chart, wired intodeployment.yamlvia the existingwith+toYamlpass-through pattern (sibling ofaffinity/tolerations).appVersion+values.yamlimage.tagto1.1.341(current latest released tag on Docker Hub).version0.4.1→0.5.0(single release for both the feature and the pin).Why
Customer asked for
topologySpreadConstraintsso they can evenly distribute replicas across availability zones. Soft pod anti-affinity (their only option today) lets the scheduler pile replicas into one zone;topologySpreadConstraints(maxSkew+whenUnsatisfiable: ScheduleAnyway) is the purpose-built primitive for even spread. The image pin to the latest release is folded in here (previously split out as #9, now closed).Compatibility
kubeVersionfloor needed.matchLabelKeysneeds 1.27+ (satisfied by all currently-supported EKS/GKE versions); noted in docs.Test plan
helm lintpasseshelm template— field omitted when unset, rendered correctly under pod spec when setkubeconform -strict(k8s 1.33) — 6/6 resources valid1.1.341confirmed as latest published semver tag on Docker HubLinear: CE-271