From 7e4e72da5fa0799b37c3a6f9a28bf67314c6fbcf Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Mon, 18 Jul 2022 16:58:32 -0700 Subject: [PATCH] Enclose in backticks so <&tag> aren't processed as HTML tags --- .../load-balancers-and-ingress/load-balancers/load-balancers.md | 2 +- .../load-balancers-and-ingress/load-balancers/load-balancers.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md b/docs/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md index 33046bd2639..097dfc1232c 100644 --- a/docs/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md +++ b/docs/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md @@ -59,7 +59,7 @@ Some cloud-managed layer-7 load balancers (such as the ALB ingress controller on Other layer-7 load balancers, such as the Google Load Balancer or Nginx Ingress Controller, directly expose one or more IP addresses. Google Load Balancer provides a single routable IP address. Nginx Ingress Controller exposes the external IP of all nodes that run the Nginx Ingress Controller. You can do either of the following: 1. Configure your own DNS to map (via A records) your domain name to the IP addresses exposes by the Layer-7 load balancer. -2. Ask Rancher to generate an xip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say a.b.c.d, and generate a host name ..a.b.c.d.xip.io. +2. Ask Rancher to generate an xip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say `a.b.c.d`, and generate a host name `..a.b.c.d.xip.io`. The benefit of using xip.io is that you obtain a working entrypoint URL immediately after you create the ingress rule. Setting up your own domain name, on the other hand, requires you to configure DNS servers and wait for DNS to propagate. diff --git a/versioned_docs/version-2.6/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md b/versioned_docs/version-2.6/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md index 9ee09220401..0e594f7efd9 100644 --- a/versioned_docs/version-2.6/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md +++ b/versioned_docs/version-2.6/v2.6/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/load-balancers.md @@ -55,7 +55,7 @@ Some cloud-managed layer-7 load balancers (such as the ALB ingress controller on Other layer-7 load balancers, such as the Google Load Balancer or Nginx Ingress Controller, directly expose one or more IP addresses. Google Load Balancer provides a single routable IP address. Nginx Ingress Controller exposes the external IP of all nodes that run the Nginx Ingress Controller. You can do either of the following: 1. Configure your own DNS to map (via A records) your domain name to the IP addresses exposes by the Layer-7 load balancer. -2. Ask Rancher to generate an xip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say a.b.c.d, and generate a host name ..a.b.c.d.xip.io. +2. Ask Rancher to generate an xip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say `a.b.c.d`, and generate a host name `..a.b.c.d.xip.io`. The benefit of using xip.io is that you obtain a working entrypoint URL immediately after you create the ingress rule. Setting up your own domain name, on the other hand, requires you to configure DNS servers and wait for DNS to propagate.