update tracing libraries for opentracing 1.6.0

[timmysilv]

What this PR does / why we need it:

This updates the opentracing C++ library to version 1.6.0 which has been available for a while. It also updates nginx-opentracing to 0.11.0, and each tracing client to the latest version that supports opentracing-cpp v1.6.0. Note that the zipkin client does not have a tagged release yet so I'm using a commit hash for now. Also, the datadog library is still on a branch. I will update this PR once DataDog/dd-opentracing-cpp#163 is merged, tagged and released.

This is helpful because there are plenty of new features in the latest opentracing version, as well as some of the tracing clients (that now depend on the new opentracing C++ library).

Notes:

• I removed -DWITH_BOOST_STATIC since it was unused
• I will update the libraries in this PR as they come out
• Once this is approved, can a maintainer run cloudbuild and update the base image?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Which issue/s this PR fixes

How Has This Been Tested?

I did some preliminary load testing to prepare for jaegertracing/jaeger-client-cpp#255, but I will do more with this exact image.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[k8s-ci-robot]

Hi @timmysilv. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[aledbf]

Build an image locally

cd images/nginx

TAG=<some tag> REGISTRY=<some personal container registry> PLATFORMS=amd64 make push

Once the image is published, open a new pull request, changing the base image defined in the Makefile
and increasing the version in the TAG file

with these two changes, the e2e tests will run, ensuring the upgrade didn't break anything (covered with tests 😉)

If e2e tests pass, the NGINX PR can be merged. After ~3 hours, a new image will be available in the staging repository.

cc @ElvinEfendi

[timmysilv]

There were lots of dependency issues, deep down a rabbit hole mostly related to the jaeger client. As a fix, I propose we build and install yaml-cpp locally, then kinda hack the jaeger client's CMakeLists.txt to not build it via sed. e2e tests are passing, and everything built fine.

[ElvinEfendi]

/ok-to-test

[ElvinEfendi]

Since the e2e tests are passing as shown in #6956

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ElvinEfendi, timmysilv

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• images/OWNERS [ElvinEfendi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment