feat: add Tailscale MagicDNS to Homepage pod, add Forgejo#14
Merged
Conversation
- DNS patch gives Homepage pod access to Tailscale MagicDNS (100.100.100.100) while preserving cluster DNS (CoreDNS) for internal services - Switch HA widget back to Tailscale hostname (now resolvable) - Add OpenClaw ping (now reachable via tailnet) - Add Forgejo card with ping - Uses ServerSideApply to merge DNS config with Helm-managed deployment
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Gives the Homepage pod direct access to the tailnet via MagicDNS, so it can resolve and query any Tailscale-exposed service.
Changes
DNS Patch (
manifests/homepage/dns-patch.yaml)dnsPolicy: Nonewith customdnsConfig100.100.100.100(Tailscale MagicDNS) +10.43.0.10(CoreDNS)cluster.localandtaile67c31.ts.netServerSideApply=true(already enabled)Homepage Values
dev-openclaw.taile67c31.ts.net:3000Why
Homepage pod couldn't resolve
*.taile67c31.ts.nethostnames because cluster DNS (CoreDNS) doesn't know about MagicDNS. This caused widget failures for any service outside the cluster.Instead of a full Tailscale sidecar, this adds Tailscale's MagicDNS resolver (
100.100.100.100) to the pod's DNS config. Much lighter — no extra containers, no auth keys, just DNS resolution.