Continental Innovates with Rancher and Kubernetes
Ingress can be added for workloads to provide load balancing, SSL termination and host/path based routing. When using ingresses in a project, you can program the ingress hostname to an external DNS by setting up a Global DNS entry.
Result: Your ingress is added to the project. The ingress begins enforcing your ingress rules.
If you choose this option, ingress routes requests to hostname to a DNS name that’s automatically generated. Rancher uses xip.io to automatically generates the DNS name. This option is best used for testing, not production environments.
Note: To use this option, you must be able to resolve to xip.io addresses.
xip.io
www.mysite.com/contact-us
www.mysite.com
/contact-us
If you use this option, ingress routes requests for a hostname to the service or workload that you specify.
Use this option to set an ingress rule for handling requests that don’t match any other ingress rules. For example, use this option to route requests that can’t be found to a 404 page.
404
Note: If you deployed Rancher using RKE, a default backend for 404s and 202s is already configured.
Note: You must have an SSL certificate that the ingress can use to encrypt/decrypt communications. For more information see Adding SSL Certificates.
Add Labels and/or Annotations to provide metadata for your ingress.
For a list of annotations available for use, see the Nginx Ingress Controller Documentation.