Skip to content

Add topologySpreadConstraints support to JaegerCommonSpec#2909

Open
ptrvsrg wants to merge 1 commit intojaegertracing:mainfrom
ptrvsrg:add_topology_spread_constraints
Open

Add topologySpreadConstraints support to JaegerCommonSpec#2909
ptrvsrg wants to merge 1 commit intojaegertracing:mainfrom
ptrvsrg:add_topology_spread_constraints

Conversation

@ptrvsrg
Copy link
Copy Markdown

@ptrvsrg ptrvsrg commented Dec 19, 2025

Which problem is this PR solving?

Description of the changes

This commit adds support for Kubernetes topologySpreadConstraints in component specifications using JaegerCommonSpec.

Changes:

  • Added TopologySpreadConstraints field to JaegerCommonSpec
  • Updated deployment and job generators to apply constraints
  • Added unit tests for the new functionality
  • Added example YAML with topology spread constraints

How was this change tested?

  • Unit tests added and passing (make test)
  • Local deployment tested with minikube
  • Example YAML validated against generated CRD
  • Backward compatibility verified (optional field with no default)

Checklist

  • Code follows the project's coding standards
  • Commit messages follow the guidelines from CONTRIBUTING_GUIDELINES.md
  • Each commit is signed (DCO)
  • Unit tests added/updated and passing
  • No breaking changes to existing APIs

This commit adds support for Kubernetes topologySpreadConstraints
in component specifications using JaegerCommonSpec.

Changes:
- Added TopologySpreadConstraints field to JaegerCommonSpec
- Updated deployment and job generators to apply constraints
- Added unit tests for the new functionality
- Added example YAML with topology spread constraints

Resolves jaegertracing#2908

Signed-off-by: ptrvsrg <s.petrov1@g.nsu.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Add topologySpreadConstraints support

1 participant