incorrect opentracing flags

[hchenxa]

What this PR does / why we need it:

Then opentracing should be on when EnableOpentracing was true.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:
/assign @caseydavenport

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hchenxa
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: caseydavenport

If they are not already assigned, you can assign the PR to them by writing /assign @caseydavenport in a comment when ready.

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:

• OWNERS

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

[aledbf]

Closing. This works as expected. When we enable opentracing (globally), some locations must be disabled. These locations are related to internal configuration of the ingress controller or health check