From 57e733f9122588bb78e5dbe63b7234e5dd1c2cb8 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 10 Aug 2020 09:46:22 -0700 Subject: [PATCH] Update content/k3s/latest/en/networking/_index.md Co-authored-by: Brad Davidson --- content/k3s/latest/en/networking/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/k3s/latest/en/networking/_index.md b/content/k3s/latest/en/networking/_index.md index afc698965a1..01247b5d8f3 100644 --- a/content/k3s/latest/en/networking/_index.md +++ b/content/k3s/latest/en/networking/_index.md @@ -3,7 +3,7 @@ title: "Networking" weight: 35 --- -This page explains how CoreDNS, the Traefik Ingress controller, and the built-in service load balancer work with K3s. +This page explains how CoreDNS, the Traefik Ingress controller, and Klipper service load balancer work within K3s. For information on CNI options, refer to the [Installation Network Options]({{}}/k3s/latest/en/installation/network-options/) page. Please reference that page for details on Flannel and the various flannel backend options or how to set up your own CNI. @@ -79,4 +79,4 @@ This is necessary if you wish to run a different LB, such as MetalLB. # Nodes Without a Hostname -Some cloud providers, such as Linode, will create machines with "localhost" as the hostname and others may not have a hostname set at all. This can cause problems with domain name resolution. You can run K3s with the `--node-name` flag or `K3S_NODE_NAME` environment variable and this will pass the node name to resolve this issue. \ No newline at end of file +Some cloud providers, such as Linode, will create machines with "localhost" as the hostname and others may not have a hostname set at all. This can cause problems with domain name resolution. You can run K3s with the `--node-name` flag or `K3S_NODE_NAME` environment variable and this will pass the node name to resolve this issue.