We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Similarly to what was done for Ingress in #439 we would need to be able to customise annotations/labels on the Jaeger Route
annotations/labels provided in the Jaeger spec are currently ignored when creating the Jaeger Route
Would you accept a PR that merges labels similarly to https://github.com/jaegertracing/jaeger-operator/blob/main/pkg/ingress/query.go#L32-L36 in https://github.com/jaegertracing/jaeger-operator/blob/main/pkg/route/query.go ?
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Requirement
Similarly to what was done for Ingress in #439 we would need to be able to customise annotations/labels on the Jaeger Route
Problem
annotations/labels provided in the Jaeger spec are currently ignored when creating the Jaeger Route
Proposal
Would you accept a PR that merges labels similarly to https://github.com/jaegertracing/jaeger-operator/blob/main/pkg/ingress/query.go#L32-L36 in https://github.com/jaegertracing/jaeger-operator/blob/main/pkg/route/query.go ?
Open questions
No response
The text was updated successfully, but these errors were encountered: