Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permanent Issue - Documentation improvements #11031

Open
longwuyuan opened this issue Feb 27, 2024 · 2 comments
Open

Permanent Issue - Documentation improvements #11031

longwuyuan opened this issue Feb 27, 2024 · 2 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@longwuyuan
Copy link
Contributor

longwuyuan commented Feb 27, 2024

What happened:

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

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

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

@longwuyuan longwuyuan added the kind/bug Categorizes issue or PR as related to a bug. label Feb 27, 2024
@k8s-ci-robot k8s-ci-robot added kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Feb 27, 2024
@rikatz rikatz removed kind/bug Categorizes issue or PR as related to a bug. kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. labels Feb 27, 2024
@k8s-ci-robot k8s-ci-robot added the needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label Feb 27, 2024
@rikatz rikatz pinned this issue Feb 27, 2024
@zengyuxing007
Copy link
Contributor

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

Copy link

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.

@github-actions github-actions bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Apr 13, 2024
@strongjz strongjz unpinned this issue Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

No branches or pull requests

4 participants