Add support for loading and configuring Jaeger as the opentracing backend

[jhorwit2]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):

jaeger

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

FEATURE

NGINX Ingress controller version:

latest

What happened:

Currently, there is only support for configuring and enabling Zipkin with opentracing. The only way to enable jaeger support is to customize the template to include the options found here

What you expected to happen:

I expect that jaeger should be easily enabled and configurable just like Zipkin.

[aledbf]

@jhorwit2 the jaeger support was added before the latest release. We will include the configuration in the next version

[andor44]

As a small correction, the custom template is not enough to get Jaeger support going, as it needs the custom Jaeger module, which is currently not compiled in nginx-ingress-controller.

[aledbf]

@andor44 I know :)
Please keep in mind the latest version of the custom nginx image contains the 0.1.1 version of the module.