Autodetect Jaeger on Kubernetes
We can deploy a variety of apps to Kubernetes, including in the future Jaeger: #5182
Customers may already have these apps deployed however, and not have a need for another version to be deployed along side. In the case of Jaeger, this is likely to be a significant waste of resources.
We should attempt to use the k8s to autodetect the presence of Jaeger, or alternative ask for the data needed to connect to it via the k8s proxy interface.
- Port (May not be required?)
This way the customer could also customize the deployment beyond what we expose.