Help us to improve the NGINX Ingress controller completing the survey
ingress-nginx is an Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer.
Learn more about Ingress on the main Kubernetes documentation site.
See the Getting Started document.
If you encounter issues, review the troubleshooting docs, file an issue, or talk to us on the #ingress-nginx channel on the Kubernetes Slack server.
Thanks for taking the time to join our community and start contributing!
- This project adheres to the Kubernetes Community Code of Conduct. By participating in this project, you agree to abide by its terms.
- See CONTRIBUTING.md for information about setting up your environment, the workflow that we expect, and instructions on the developer certificate of origin that we require.
- Check out the open issues.
- Join our Kubernetes Slack channel: #ingress-nginx
See the list of releases to find out about feature changes For detailed changes for each release; please check the Changelog.md
- 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 in the #ingress-nginx channel to ask questions to get support from the maintainers and other users
- The github issues in the repository are exclusively for bug reports and feature requests.
- Discuss: Tweet using the
#IngressNginxhashtag
Build and push nginx-fips image nginx readme
Set BASE_IMAGE env to nginx-fips image
export BASE_IMAGE=infoblox/nginx-fips:20200908-bcd33a8d2
Set REGISTRY env to controller docker hub repo
export REGISTRY=<your docker registry>
Set TAG env to your image version
export TAG=<your image tag>
Build image
make image
Build and push
make release
Please make sure to read the Issue Reporting Checklist before opening an issue. Issues not conforming to the guidelines may be closed immediately.