From 491ffa820938e65729884aee8d02e9410a5290e9 Mon Sep 17 00:00:00 2001 From: Devin Buhl Date: Mon, 9 Dec 2024 20:37:55 -0500 Subject: [PATCH] chore: update readme Signed-off-by: Devin Buhl --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 7abd6741ebf..21140fded4e 100644 --- a/README.md +++ b/README.md @@ -231,10 +231,14 @@ _Mic check, 1, 2_ - In a few moments applications should be lighting up like Chr #### 🌐 Public DNS + 📍 _Use the `external` ingress class to make applications public to the internet_ + The `external-dns` application created in the `networking` namespace will handle creating public DNS records. By default, `echo-server` and the `flux-webhook` are the only subdomains reachable from the public internet. In order to make additional applications public you must set set the correct ingress class name and ingress annotations like in the HelmRelease for `echo-server`. #### 🏠 Home DNS + 📍 _Use the `internal` ingress class to make applications private to your network_ + `k8s_gateway` will provide DNS resolution to external Kubernetes resources (i.e. points of entry to the cluster) from any device that uses your home DNS server. For this to work, your home DNS server must be configured to forward DNS queries for `${bootstrap_cloudflare.domain}` to `${bootstrap_cloudflare.gateway_vip}` instead of the upstream DNS server(s) it normally uses. This is a form of **split DNS** (aka split-horizon DNS / conditional forwarding). > [!TIP]