- NGINX Ingress controller changes in Kubernetes v1.21
- Automatically generate a xip.io hostname
- Specify a hostname to use
- Use as the default backend
- Labels and Annotations
NGINX Ingress controller changes in Kubernetes 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.
Ingress Rule Configuration
Specify a hostname to use
If you use this option, ingress routes requests for a hostname to the service or workload that you specify.
- Enter the Request Host that your ingress will handle request forwarding for. For example,
- Add a Target Service.
- Optional: If you want specify a workload or service when a request is sent to a particular hostname path, add a Path for the target. For example, if you want requests for
www.mysite.com/contact-usto be sent to a different service than
/contact-usin the Path field. Typically, the first rule that you create does not include a path.
Enter the Port number that each target operates on.
Note: You must have an SSL certificate that the ingress can use to encrypt/decrypt communications. For more information see Adding SSL Certificates.
When creating an ingress, click the Certificates tab.
Click Add Certificate.
Select a Certificate - Secret Name from the drop-down list.
Enter the host using encrypted communication.
To add additional hosts that use the certificate, click Add Hosts.
Labels and Annotations
For a list of annotations available for use, see the Nginx Ingress Controller Documentation.