Gary Brown

> as pills in the trace row in the Search result? Yes, although presented slightly differently to make it clear not a traced service > in the Services dropdown on...

This would be in preparation for supporting storage that only addresses a subset of the queries - e.g. index storage for searches, and blob storage for trace id lookups.

@harpratap Would you be interested in contributing a PR to fix this?

@izelnakri This is probably due to the description fields being stripped from the CRD, which was necessary due to its size - when using `kubectl apply` it failed. See https://github.com/jaegertracing/jaeger-operator/issues/854.

Sounds like a good idea to me. Would be good to run performance/scaling tests though.

@jpkrohling Thought the dynamic queue size enhancement would avoid such situations?

Agree this should probably be restricted to those components that actually access kafka - however not sure it is a big security issue, as it is only available to the...

Don't you mean https://github.com/jaegertracing/jaeger-operator/blob/master/.ci/release.sh#L73 - looks like it is mapping the version tag to master?

Looks like it has been in since the beginning: https://github.com/jaegertracing/jaeger-operator/commit/c5c97aea0b151b328816013b723610a90654ddc6#diff-0ade8a06d51b947d7705c1a9ae1bab59 The tags push has been in since the initial comment: https://github.com/jaegertracing/jaeger-operator/commit/dd0cd3b537268e0fe7a670eb6edd63493735cf29#diff-0ade8a06d51b947d7705c1a9ae1bab59 We should fix before next release - but need...

@ctron Hi. I assume you are running on OpenShift? Can you confirm the version you were upgrading from?