From 09ce7e572a378fc8eef6db1fc159c79295abe2fd Mon Sep 17 00:00:00 2001 From: Travis Bot Date: Fri, 14 Sep 2018 00:19:30 +0000 Subject: [PATCH] Deploy GitHub Pages --- deploy/baremetal/index.html | 12 ++--- sitemap.xml | 90 ++++++++++++++++++------------------ sitemap.xml.gz | Bin 219 -> 219 bytes 3 files changed, 51 insertions(+), 51 deletions(-) diff --git a/deploy/baremetal/index.html b/deploy/baremetal/index.html index fe68e29e7..d65645859 100644 --- a/deploy/baremetal/index.html +++ b/deploy/baremetal/index.html @@ -1186,8 +1186,8 @@ suffices to provide a single point of contact to the NGINX Ingress controller to external clients and, indirectly, to any application running inside the cluster. Bare-metal environments lack this commodity, requiring a slightly different setup to offer the same kind of access to external consumers.

-

Cloud environment -Bare-metal environment

+

Cloud environment +Bare-metal environment

The rest of this document describes a few recommended approaches to deploying the NGINX Ingress controller inside a Kubernetes cluster running on bare-metal.

A pure software solution: MetalLB

@@ -1196,7 +1196,7 @@ supported cloud provider, effectively allowing the usage of LoadBalancer Service

This section demonstrates how to use the Layer 2 configuration mode of MetalLB together with the NGINX Ingress controller in a Kubernetes cluster that has publicly accessible nodes. In this mode, one node attracts all the traffic for the ingress-nginx Service IP. See Traffic policies for more details.

-

MetalLB in L2 mode

+

MetalLB in L2 mode

Note

The description of other supported configuration modes is off-scope for this document.

@@ -1273,7 +1273,7 @@ any port, including the standard HTTP ports 80 and 443. However, due to the cont 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

+

NodePort request flow

Example

Given the NodePort 30100 allocated to the ingress-nginx Service

@@ -1454,7 +1454,7 @@ of a traditional Deployment.

Because most properties of DaemonSet objects are identical to Deployment objects, this documentation page leaves the configuration of the corresponding manifest at the user's discretion.

-

DaemonSet with hostNetwork flow

+

DaemonSet with hostNetwork flow

Like with NodePorts, this approach has a few quirks it is important to be aware of.