Add HTTP Port 5778

[Aergonus]

https://www.jaegertracing.io/docs/deployment/#agent

$ grep -r 5775 *
all-in-one/jaeger-all-in-one-template.yml:                - containerPort: 5775
all-in-one/jaeger-all-in-one-template.yml:      port: 5775
all-in-one/jaeger-all-in-one-template.yml:      targetPort: 5775
jaeger-production-template.yml:          - containerPort: 5775
README.md:          - containerPort: 5775
README.md:The Jaeger Agent will then be available to your application at `localhost:5775`/`localhost:6831`/`localhost:6832`/`localhost:5778`.
$ grep -r 5778 *
all-in-one/jaeger-all-in-one-template.yml:                - containerPort: 5778
all-in-one/jaeger-all-in-one-template.yml:      port: 5778
all-in-one/jaeger-all-in-one-template.yml:      targetPort: 5778
jaeger-production-template.yml:          - containerPort: 5778
README.md:          - containerPort: 5778
README.md:The Jaeger Agent will then be available to your application at `localhost:5775`/`localhost:6831`/`localhost:6832`/`localhost:5778`.

Signed-off-by: Victor Lei klei22@bloomberg.net

[Aergonus]

I'm not sure if this should be changed

[jpkrohling]

Yes, I believe so.

[Aergonus]

Addresses #91

[jpkrohling]

Thank you for this PR! It looks good to me, but Travis is failing due to:

[WARNING] Missing header in: /home/travis/build/jaegertracing/jaeger-kubernetes/all-in-one/jaeger-all-in-one-template.yml

You can fix it by running ./mvnw license:format. Once this is fixed, I'll merge this PR.

[Aergonus]

It's quite ridiculous to me that it's up to an external contributor to keep the license up to date... Not to mention I'm working behind proxies I don't control so mvnw doesn't work.

Travis jobs have been broken since #89 at least

[jpkrohling]

I feel your pain!

It's quite ridiculous to me that it's up to an external contributor to keep the license up to date

This is not always the case, but it's the first time this file was changed this year, so, the license checker requires this update.

Travis jobs have been broken since #89 at least

Indeed, just wanted to avoid one more reason for it to be broken ;-)

@jkandasa, @kevinearls, do you know why the CI tests are broken?

[jpkrohling]

Looks like the tests are failing intermittently.

[pavolloffay]

c* sometimes fails. it has to be manually restarted

[jpkrohling]

Our integration tests are really far from being reliable... I had also to restart ES's job.

[Aergonus]

I'll push a no-op update to the other PR so it can rerun the CI tests