Help us to improve the NGINX Ingress controller completing the survey
- Contributing: Pull requests are welcome!
- Read
CONTRIBUTING.mdand check out help-wanted issues - Submit github issues for any feature enhancements, bugs or documentation problems
- Read
- Support: Join to Kubernetes Slack to ask questions to get support from the maintainers and other developers
- Questions/comments can also be posted as github issues
- Discuss: Tweet using the
#IngressNginxhashtag
This repository contains the NGINX controller built around the Kubernetes Ingress resource that uses ConfigMap to store the NGINX configuration.
Learn more about using Ingress on k8s.io
Configuring a webserver or loadbalancer is harder than it should be. Most webserver configuration files are very similar. There are some applications that have weird little quirks that tend to throw a wrench in things, but for the most part you can apply the same logic to them and achieve a desired result.
The Ingress resource embodies this idea, and an Ingress controller is meant to handle all the quirks associated with a specific "class" of Ingress.
An Ingress Controller is a daemon, deployed as a Kubernetes Pod, that watches the apiserver's /ingresses endpoint for updates to the Ingress resource. Its job is to satisfy requests for Ingresses.
To check out Live Docs
For questions and support please use the kubernetes-users room in the Kubernetes Slack or kubernetes-users mailing list. The issue list of this repo is exclusively for bug reports and feature requests.
Please make sure to read the Issue Reporting Checklist before opening an issue. Issues not conforming to the guidelines may be closed immediately.
Detailed changes for each release are documented in the CHANGELOG.md
Please make sure to read the Contributing Guide before making a pull request.
Thank you to all the people who already contributed to NGINX Ingress Controller!
This project adheres to the Kubernetes Community Code of Conduct. By participating in this project you agree to abide by its terms.