feat(chart): support Service trafficDistribution - #6930
Open
younsl wants to merge 1 commit into
Open
Conversation
Add `service.trafficDistribution` and `pairingRelay.service.trafficDistribution` so operators can enable topology-aware routing on the relay and pairing relay Services. Empty (the default) omits `spec.trafficDistribution` entirely, so rendered manifests are unchanged for existing installs. The schema restricts values to the ones the API server accepts (`PreferClose`, `PreferSameZone`, `PreferSameNode`), catching typos at install time rather than at apply time. Release chart 0.1.9. Signed-off-by: younsl <cysl@kakao.com>
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
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
Adds optional Service spec.trafficDistribution to the relay and pairing relay Services so operators can enable topology-aware routing and cut cross-zone traffic.
New values, both empty by default:
Empty omits the field, so rendered manifests are unchanged for existing installs. The schema restricts values to PreferClose, PreferSameZone, and PreferSameNode, so a typo fails at install time instead of at apply time. Releases chart 0.1.9.
Related issue
None found.
Testing
helm unittest: 47 passed, including 3 new cases covering the default omission, PreferClose on the relay Service, and PreferSameZone on the pairing relay Service. The 3 pre-existing failures on this branch also fail on main and come from a local plugin version difference (1.0.3 vs the 0.8.2 pinned in CI).
Schema enum accept and reject verified directly against values.schema.json. helm template and ct lint were not run locally because the OCI subchart dependencies could not be fetched; CI covers both.
No UI change.