Remove opentracing and zipkin components mentions from docs

[LucasAndFlores]

What this PR does / why we need it:

• Remove opentracing from third party addons section
• Remove opentracing and zipkin mentions from User guide/nginx-configuration/configmap
• Remove opentracing and zipkin mentions from User-guide/nginx-configuration/annotations

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• CVE Report (Scanner found CVE and adding report)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation only

Which issue/s this PR fixes

fixes #11042

How Has This Been Tested?

You can run the command live-docs and check the docs updated.

Checklist:

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: LucasAndFlores / name: Lucas Andrade Flores (2b26337)

[k8s-ci-robot]

Welcome @LucasAndFlores!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-nginx has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @LucasAndFlores. 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-sigs/prow repository.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

Name	Link
🔨 Latest commit	2b26337
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/66450deb114a1a0008cb8173

[longwuyuan]

@LucasAndFlores thank you for this contribution. Helps.

• Are completely done with this or is there more opentracing related cleanup you are looking at.
• Do you intend to work on removing zipkin or other content also.

I think we can go ahead with this if there is no more changes you are expecting to make. I will also check if there is any tiny nits

/kind documentation
/triage accepted
/ok-to-test

[longwuyuan]

@LucasAndFlores there is a github bot to squash commits. But if its possible, please consider to squash your commits yourself. Just to help as history here can be relatively cleaner that way. thank you

[LucasAndFlores]

@longwuyuan Sure, I'll squash the commits. And from my side, I don't see any other change. If you find something necessary to change, tag me and I can make it.

[LucasAndFlores]

@longwuyuan The squash is done 🙂 If any other change is necessary, feel free to tag me.

[longwuyuan]

I see the significant reference to opentracing and zipkin gone. So maybe better to get this done first. If tnere are nits I missed,, maybe we can create a new issue to track the remianing work.

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: longwuyuan, LucasAndFlores

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:

• docs/OWNERS [longwuyuan]

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

[Gacko]

/cherry-pick release-1.10

[k8s-infra-cherrypick-robot]

@Gacko: #11361 failed to apply on top of branch "release-1.10":

Applying: Docs: Remove opentracing and zipkin from docs
Using index info to reconstruct a base tree...
M	docs/user-guide/nginx-configuration/annotations.md
M	docs/user-guide/nginx-configuration/configmap.md
Falling back to patching base and 3-way merge...
Removing docs/user-guide/third-party-addons/opentracing.md
Auto-merging docs/user-guide/nginx-configuration/configmap.md
CONFLICT (content): Merge conflict in docs/user-guide/nginx-configuration/configmap.md
Auto-merging docs/user-guide/nginx-configuration/annotations.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Docs: Remove opentracing and zipkin from docs
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.10

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-sigs/prow repository.