412cd70d3a
Adds the ability to create alternative backends. Alternative backends enable traffic shaping by sharing a single location but routing to different backends depending on the TrafficShapingPolicy defined by AlternativeBackends. When the list of upstreams and servers are retrieved, we then call mergeAlternativeBackends which iterates through the paths of every ingress and checks if the backend supporting the path is a AlternativeBackend. If so, we then iterate through the map of servers and find the real backend that the AlternativeBackend should fall under. Once found, the AlternativeBackend is embedded in the list of VirtualBackends for the real backend. If no matching real backend for a AlternativeBackend is found, then the AlternativeBackend is deleted as it cannot be backed by any server. |
||
|---|---|---|
| .github | ||
| .travis | ||
| build | ||
| cmd/nginx | ||
| deploy | ||
| docs | ||
| hack | ||
| images | ||
| internal | ||
| rootfs | ||
| test | ||
| vendor | ||
| version | ||
| .codecov.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .luacheckrc | ||
| .travis.yml | ||
| Changelog.md | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| labels.yaml | ||
| LICENSE | ||
| Makefile | ||
| mkdocs.yml | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| README.md | ||
| requirements-docs.txt | ||
| SECURITY_CONTACTS | ||
Help us to improve the NGINX Ingress controller completing the survey
NGINX Ingress Controller
Get Involved
- 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
Description
This repository contains the NGINX controller built around the Kubernetes Ingress resource that uses ConfigMap to store the NGINX configuration. Make Ingress-Nginx Work for you, and the Community from KubeCon Europe 2018 is a great video to get you started!!
Learn more about using Ingress on k8s.io
What is an Ingress Controller?
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.
Documentation
To check out Live Docs
Questions
For questions and support please use the #ingress-nginx channel in the Kubernetes Slack or post to the Kubernetes Forum. The issue list of this repo is exclusively for bug reports and feature requests.
Issues
Please make sure to read the Issue Reporting Checklist before opening an issue. Issues not conforming to the guidelines may be closed immediately.
Changelog
Detailed changes for each release are documented in the Changelog.md
Contribution
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!
Code of Conduct
This project adheres to the Kubernetes Community Code of Conduct. By participating in this project you agree to abide by its terms.