From dc98887a1421e9218694b846721d2a188601ce20 Mon Sep 17 00:00:00 2001 From: Vito Botta Date: Fri, 22 Sep 2023 19:53:51 +0300 Subject: [PATCH] Improve text --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f0e9f9c..423a522 100644 --- a/README.md +++ b/README.md @@ -225,7 +225,7 @@ This will take a few minutes depending on the number of masters and worker nodes ### Disabling public IPs (IPv4 or IPv6 or both) on nodes -With `enable_public_net_ipv4: false` and `enable_public_net_ipv6: false` you can disable the public interface for all nodes for improved security. These settings are global and effects all master and worker nodes. If you disable public IPs be sure to run hetzer-k3s from a machine that has access to the same private network as the nodes either directly or via some VPN. +With `enable_public_net_ipv4: false` and `enable_public_net_ipv6: false` you can disable the public interface for all nodes for improved security and saving on ipv4 addresses costs. These settings are global and effects all master and worker nodes. If you disable public IPs be sure to run hetzer-k3s from a machine that has access to the same private network as the nodes either directly or via some VPN. Additional networking setup is required via cloud init, so it's important that the machine from which you run hetzner-k3s have internet access and DNS configured correctly, otherwise the cluster creation process will get stuck after creating the nodes. See [this discussion](https://github.com/vitobotta/hetzner-k3s/discussions/252) for additional information and instructions. ### Using alternative OS images