Nginx Ingress still referenced
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 273
- Forks
- 391
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this?
- I have searched the existing issues
Description
Hello,
the Nginx Ingress controller is no longer maintained since march, 24 2026. https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/
Few pages in the document still referenced it :
https://support.us.ovhcloud.com/hc/en-us/articles/33380894927891-Expose-your-app-deployed-on-an-OVHcloud-Managed-Kubernetes-Service
https://support.us.ovhcloud.com/hc/en-us/articles/1500004961501-Installing-Nginx-Ingress-on-OVHcloud-Managed-Kubernetes
It would be great to display a warning about using it.
Guillaume
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the repository for references matching the two linked OVHcloud support pages, “Expose your app deployed on an OVHcloud Managed Kubernetes Service” and “Installing Nginx Ingress on OVHcloud Managed Kubernetes.” Review their current Nginx Ingress guidance and add the requested warning; the work is done when both referenced pages clearly warn readers about its maintenance status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100