diff --git a/deploy/baremetal/index.html b/deploy/baremetal/index.html index ad14be86b..4d1aa1447 100644 --- a/deploy/baremetal/index.html +++ b/deploy/baremetal/index.html @@ -22,7 +22,7 @@

As soon as MetalLB sets the external IP address of the ingress-nginx LoadBalancer Service, the corresponding entries are created in the iptables NAT table and the node with the selected IP address starts responding to HTTP requests on the ports configured in the LoadBalancer Service:

$ curl -D- http://203.0.113.10 -H 'Host: myapp.example.com'
 HTTP/1.1 200 OK
 Server: nginx/1.15.2
-

Tip

In order to preserve the source IP address in HTTP requests sent to NGINX, it is necessary to use the Local traffic policy. Traffic policies are described in more details in Traffic policies as well as in the next section.

Over a NodePort Service

Due to its simplicity, this is the setup a user will deploy by default when following the steps described in the installation guide.

Info

A Service of type NodePort exposes, via the kube-proxy component, the same unprivileged port (default: 30000-32767) on every Kubernetes node, masters included. For more information, see Services.

In this configuration, the NGINX container remains isolated from the host network. As a result, it can safely bind to any port, including the standard HTTP ports 80 and 443. However, due to the container namespace isolation, a client located outside the cluster network (e.g. on the public internet) is not able to access Ingress hosts directly on ports 80 and 443. Instead, the external client must append the NodePort allocated to the ingress-nginx Service to HTTP requests.

NodePort request flow

Example

Given the NodePort 30100 allocated to the ingress-nginx Service

$ kubectl -n ingress-nginx get svc
+

Tip

In order to preserve the source IP address in HTTP requests sent to NGINX, it is necessary to use the Local traffic policy. Traffic policies are described in more details in Traffic policies as well as in the next section.

Over a NodePort Service

Due to its simplicity, this is the setup a user will deploy by default when following the steps described in the installation guide.

Info

A Service of type NodePort exposes, via the kube-proxy component, the same unprivileged port (default: 30000-32767) on every Kubernetes node, masters included. For more information, see Services.

In this configuration, the NGINX container remains isolated from the host network. As a result, it can safely bind to any port, including the standard HTTP ports 80 and 443. However, due to the container namespace isolation, a client located outside the cluster network (e.g. on the public internet) is not able to access Ingress hosts directly on ports 80 and 443. Instead, the external client must append the NodePort allocated to the ingress-nginx Service to HTTP requests.

NodePort request flow

Example

Given the NodePort 30100 allocated to the ingress-nginx Service

$ kubectl -n ingress-nginx get svc
 NAME                   TYPE        CLUSTER-IP     PORT(S)
 default-http-backend   ClusterIP   10.0.64.249    80/TCP
 ingress-nginx          NodePort    10.0.220.217   80:30100/TCP,443:30101/TCP
diff --git a/deploy/index.html b/deploy/index.html
index abd7b20f7..f20c09539 100644
--- a/deploy/index.html
+++ b/deploy/index.html
@@ -29,7 +29,7 @@

Scaleway

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.0.4/deploy/static/provider/scw/deploy.yaml

Exoscale

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/exoscale/deploy.yaml

The full list of annotations supported by Exoscale is available in the Exoscale Cloud Controller Manager documentation.

Oracle Cloud Infrastructure

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.0.4/deploy/static/provider/cloud/deploy.yaml
-

A complete list of available annotations for Oracle Cloud Infrastructure can be found in the OCI Cloud Controller Manager documentation.

Bare metal clusters

Using NodePort:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.0.4/deploy/static/provider/baremetal/deploy.yaml
+

A complete list of available annotations for Oracle Cloud Infrastructure can be found in the OCI Cloud Controller Manager documentation.

Bare metal clusters

Using NodePort:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.0.4/deploy/static/provider/baremetal/deploy.yaml

Tip

Applicable on kubernetes clusters deployed on bare-metal with generic Linux distro(Such as CentOs, Ubuntu ...).

Info

For extended notes regarding deployments on bare-metal, see Bare-metal considerations.

Miscellaneous

Checking ingress controller version

Run nginx-ingress-controller --version within the pod, for instance with kubectl exec:

POD_NAMESPACE=ingress-nginx
 POD_NAME=$(kubectl get pods -n $POD_NAMESPACE -l app.kubernetes.io/name=ingress-nginx --field-selector=status.phase=Running -o name)
 kubectl exec $POD_NAME -n $POD_NAMESPACE -- /nginx-ingress-controller --version
diff --git a/sitemap.xml b/sitemap.xml
index 3d6c21867..0713d8e41 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,207 +1,207 @@
 
 
      https://kubernetes.github.io/ingress-nginx/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/how-it-works/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/troubleshooting/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/kubectl-plugin/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/deploy/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/deploy/baremetal/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/deploy/rbac/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/deploy/upgrade/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/deploy/hardening-guide/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/basic-usage/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/custom-template/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/log-format/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/cli-arguments/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/custom-errors/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/default-backend/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/fcgi-services/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/ingress-path-matching/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/external-articles/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/miscellaneous/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/monitoring/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/multiple-ingress/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/tls/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/third-party-addons/modsecurity/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/user-guide/third-party-addons/opentracing/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/PREREQUISITES/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/affinity/cookie/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/auth/basic/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/auth/client-certs/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/auth/external-auth/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/auth/oauth-external-auth/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/customization/configuration-snippets/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/customization/custom-configuration/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/customization/custom-errors/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/customization/custom-headers/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/customization/external-auth-headers/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/customization/ssl-dh-param/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/customization/sysctl/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/docker-registry/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/grpc/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/multi-tls/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/rewrite/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/static-ip/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/tls-termination/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/examples/psp/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/developer-guide/getting-started/
-     2021-11-09
+     2021-11-11
      daily
     
      https://kubernetes.github.io/ingress-nginx/developer-guide/code-overview/
-     2021-11-09
+     2021-11-11
      daily
     
 
\ No newline at end of file
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index 85004d5cd..b16d589c9 100644
Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ