Permanent Issue - Documentation improvements

[longwuyuan]

What happened:

• This issue is a permanent issue
• This issue will list and track improvements to documentation https://kubernetes.github.io/ingress-nginx/
• Th

What you expected to happen:

Remove content related to deprecated & unsupported components

• Opentracing, zipkin etc are some components that are not supported anymore but there is lingering content in the docs on these components

AWS EKS use cases

Project does not have a AWS account to test and verify this repeatedly (like in CI) so any contributions are welcome

Requirement of the new AWS LB Controller to launch a NLB

• https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/

Both External & Internal LB created from one single install of the ingress-nginx controller

• Currently, there is a feature available to create both internal as well as a external LB from one single installation instance of the ingress-nginx controller
• This use-case gets complicated when users integrate external-dns in the scene
• The external-dns app does not get/usetake the internal-nlb hostname because the controller can not return the internal-nlb hostname to external-dns

False positive on using the internal-lb annotation

• It is suspected that the NLB created, even after configuring the the internal-lb annotation, is actually a internet-facing NLB

OpenTelemetry use-cases

• Traces for both ingress-nginx controller as client as well as server OpenTelemetry: Need to emits two spans (server and client) #11002 @esigo

PSA instead of PSP docs

CORS use-cases for newbies to CORS

Canary use-case examples simplified

AZURE use-cases

• Azure specific annotation needed for health-check probe

/kind deprecation
/priority important-longterm
/triage accepted

[zengyuxing007]

There are many Nginx ingress users on Alibaba Cloud ACK, and I am glad to submit some related user cases on Alibaba Cloud.

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.