public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-19 19:35:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

NGINX Ingress controller changes in v1.21

Browse Source
This commit is contained in:
Jennifer Travinski
2021-08-20 14:34:56 -04:00
parent c483d6d3d8
commit bb52f4b06f
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/ingress-config/_index.md
+6 -1
View File
@@ -1,15 +1,20 @@
---
title: Ingress Rule Configuration
title: Ingress Configuration
description: Ingress configuration
weight: 9999
---
- [NGINX Ingress controller changes in v1.21](#nginx-ingress-controller-changes-in-v1-21)
- [Automatically generate a xip.io hostname](#automatically-generate-a-xip-io-hostname)
- [Specify a hostname to use](#specify-a-hostname-to-use)
- [Use as the default backend](#use-as-the-default-backend)
- [Certificates](#certificates)
- [Labels and Annotations](#labels-and-annotations)
### NGINX Ingress controller changes in v1.21
For Kubernetes v1.21 and up, the NGINX Ingress controller no longer runs in hostNetwork but uses hostPorts for port 80 and port 443. This was done so the admission webhook can be configured to be accessed using ClusterIP so it can only be reached inside the cluster.
### Automatically generate a xip.io hostname
If you choose this option, ingress routes requests to hostname to a DNS name that's automatically generated. Rancher uses [xip.io](http://xip.io/) to automatically generates the DNS name. This option is best used for testing, _not_ production environments.