feat: add serviceAnnotations and trafficDistribution to service templates (PR 4090)#4113
Merged
dhruv-shah-sumo merged 5 commits intomainfrom Mar 17, 2026
Merged
feat: add serviceAnnotations and trafficDistribution to service templates (PR 4090)#4113dhruv-shah-sumo merged 5 commits intomainfrom
dhruv-shah-sumo merged 5 commits intomainfrom
Conversation
…ce templates Add configurable serviceAnnotations and trafficDistribution fields to the logs collector, metadata logs, and metrics service templates. This enables Kubernetes topology-aware routing (trafficDistribution: PreferClose) and the topology-mode annotation to reduce cross-zone data transfer costs. New values: - metadata.serviceAnnotations / metadata.trafficDistribution - otellogs.serviceAnnotations / otellogs.trafficDistribution Co-Authored-By: Claude <[email protected]>
Add towncrier changelog entry for the new serviceAnnotations and trafficDistribution feature. Document new config keys in the Helm chart README for metadata.* and otellogs.* sections. Co-Authored-By: Claude <[email protected]>
Add README entries for the new serviceAnnotations and trafficDistribution parameters for both metadata and otellogs services after merging main. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Rename changelog file to reflect the correct PR number. Co-Authored-By: Claude Opus 4.6 <[email protected]>
Collaborator
Author
|
More context for internal discussions: https://sumologic.slack.com/archives/C09BL6UQ75Y/p1773199775247959 |
Gourav2906
approved these changes
Mar 17, 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
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 PR is copied from #4090
Thanks to @abebars for introducing this changes.
Summary
Add configurable serviceAnnotations and trafficDistribution fields to the logs collector, metadata logs, and metrics service templates. This enables Kubernetes topology-aware routing to reduce cross-zone data transfer costs.
Motivation
Kubernetes 1.27+ supports trafficDistribution: PreferClose on Services, which routes traffic to endpoints in the same zone when possible. Combined with the service.kubernetes.io/topology-mode: Auto annotation, this significantly reduces cross-zone network costs in multi-AZ clusters.
Currently, there's no way to set these fields on the chart's services without maintaining local patches.
Changes
Templates modified (3 files):
templates/logs/collector/common/service.yaml— usesotellogs.serviceAnnotations / otellogs.trafficDistributiontemplates/logs/common/service.yaml— usesmetadata.serviceAnnotations / metadata.trafficDistributiontemplates/metrics/common/service.yaml— usesmetadata.serviceAnnotations / metadata.trafficDistributionvalues.yaml defaults:
Usage
References
Kubernetes Topology Aware Routing
KEP-4444: Traffic Distribution for Services
Checklist