DevFW-CICD/ingress-nginx-helm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Linkable baremetal sub-sections

Browse source
This commit is contained in:
dmotte 2025-01-21 01:50:13 +01:00 committed by k8s-infra-cherrypick-robot
parent 8bf144cc97
commit 9dd78c7cf9
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/deploy/baremetal.md
View file

@ -152,7 +152,7 @@ requests.
This approach has a few other limitations one ought to be aware of: This approach has a few other limitations one ought to be aware of:
* **Source IP address** ### Source IP address
Services of type NodePort perform [source address translation][nodeport-nat] by default. This means the source IP of a Services of type NodePort perform [source address translation][nodeport-nat] by default. This means the source IP of a
HTTP request is always **the IP address of the Kubernetes node that received the request** from the perspective of HTTP request is always **the IP address of the Kubernetes node that received the request** from the perspective of
@ -191,7 +191,7 @@ field of the `ingress-nginx` Service spec to `Local` ([example][preserve-ip]).
Requests sent to `host-2` and `host-3` would be forwarded to NGINX and original client's IP would be preserved, Requests sent to `host-2` and `host-3` would be forwarded to NGINX and original client's IP would be preserved,
while requests to `host-1` would get dropped because there is no NGINX replica running on that node. while requests to `host-1` would get dropped because there is no NGINX replica running on that node.
* **Ingress status** ### Ingress status
Because NodePort Services do not get a LoadBalancerIP assigned by definition, the Ingress-Nginx Controller **does not Because NodePort Services do not get a LoadBalancerIP assigned by definition, the Ingress-Nginx Controller **does not
update the status of Ingress objects it manages**. update the status of Ingress objects it manages**.
@ -241,7 +241,7 @@ Service.
test-ingress myapp.example.com 203.0.113.1,203.0.113.2,203.0.113.3 80 test-ingress myapp.example.com 203.0.113.1,203.0.113.2,203.0.113.3 80
``` ```
* **Redirects** ### Redirects
As NGINX is **not aware of the port translation operated by the NodePort Service**, backend applications are responsible As NGINX is **not aware of the port translation operated by the NodePort Service**, backend applications are responsible
for generating redirect URLs that take into account the URL used by external clients, including the NodePort. for generating redirect URLs that take into account the URL used by external clients, including the NodePort.
@ -326,13 +326,13 @@ configuration of the corresponding manifest at the user's discretion.
Like with NodePorts, this approach has a few quirks it is important to be aware of. Like with NodePorts, this approach has a few quirks it is important to be aware of.
* **DNS resolution** ### DNS resolution
Pods configured with `hostNetwork: true` do not use the internal DNS resolver (i.e. *kube-dns* or *CoreDNS*), unless Pods configured with `hostNetwork: true` do not use the internal DNS resolver (i.e. *kube-dns* or *CoreDNS*), unless
their `dnsPolicy` spec field is set to [`ClusterFirstWithHostNet`][dnspolicy]. Consider using this setting if NGINX is their `dnsPolicy` spec field is set to [`ClusterFirstWithHostNet`][dnspolicy]. Consider using this setting if NGINX is
expected to resolve internal names for any reason. expected to resolve internal names for any reason.
* **Ingress status** ### Ingress status
Because there is no Service exposing the Ingress-Nginx Controller in a configuration using the host network, the default Because there is no Service exposing the Ingress-Nginx Controller in a configuration using the host network, the default
`--publish-service` flag used in standard cloud setups **does not apply** and the status of all Ingress objects remains `--publish-service` flag used in standard cloud setups **does not apply** and the status of all Ingress objects remains