Gary Brown

@wu-sheng I've added a similar suggestion to https://github.com/opentracing-contrib/java-observer/pull/3#issuecomment-313618255 - although the valid point made by @felixbarny is that it adds complexity where in most cases there will only be a...

@pavolloffay @jpkrohling Could review please? Notes: * This PR includes basic instrumentation rules for demarcating Wildfly/EAP EJB usage. So is not a general EJB instrumentation approach - this could be...

Agree automated is better, but depends whether we should have a set of tests that depend on a separate server to be launched (not sure how many of the agent...

@ammendonca Great work! Marked as 'do not merge' for now until we sort out the backend.

@pat2man Sorry for the delay in responding. Although this UI is great, we have recently made the decision to use the Jaeger project as our OpenTracing core - which already...

Doesn't look like kubernetes or openshift understands ranges. We have been referring to these templates as 'production' versions - and as stated https://kubernetes.io/docs/concepts/configuration/overview/#container-images use of 'latest' in production is not...

Great job!

General question: What are the implications if the CR enables and then disables these options? (same for normal storage i.e. non-archive). Do we need the operator to perform any additional...

@jpkrohling Is there any way the operator could prevent such upgrades? i.e. if user goes from a valid to an invalid state - prevent the invalid state being acted upon?

@jpkrohling Just a naming comment - as they are related to the jaeger instances, rather than the operator, should they be `jaeger_instances_by_...`? May be "operator" could be a label specifying...