public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-25 14:18:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update content/k3s/latest/en/networking/_index.md

Browse Source 
Co-authored-by: Brad Davidson <brad@oatmail.org>
This commit is contained in:
Catherine Luse
2020-08-10 09:46:22 -07:00
parent 5579c35692
commit 57e733f912
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/k3s/latest/en/networking/_index.md
+2 -2
View File
@@ -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]({{<baseurl>}}/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.
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.