You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a homelab with k3s. External dns works with core dns. I figure why not use that as my internal dns for my homelab. Now days, it's not even too hard to expose dns with a Service LB with metal-lb or kube-vip.
Just wondering if anyone has been daring enough to try this?
I figure it would involve adding a zone to the configuration and somehow only exposing that zone so I don't expose the whole internal service network to my whole network.
Also seems I would have to expose the etcd under the cluster which is installed by k3s. However, I don't know much about etcd, for example can I even have multiple "databases" like mysql?
Maybe I just end up installing an etcd in my cluster and a separate coredns. But if I have to do that, well . . . I already got some BIND laying around and that's another questionable battle with external dns.
Any ideas on what else I would have to do. Like I'm confident enough to give it a shot but there are a ton of unknowns here and this sounds like tedious trial and error unless there is at least some guidance if any.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a homelab with k3s. External dns works with core dns. I figure why not use that as my internal dns for my homelab. Now days, it's not even too hard to expose dns with a Service LB with metal-lb or kube-vip.
Just wondering if anyone has been daring enough to try this?
I figure it would involve adding a zone to the configuration and somehow only exposing that zone so I don't expose the whole internal service network to my whole network.
Also seems I would have to expose the etcd under the cluster which is installed by k3s. However, I don't know much about etcd, for example can I even have multiple "databases" like mysql?
Maybe I just end up installing an etcd in my cluster and a separate coredns. But if I have to do that, well . . . I already got some BIND laying around and that's another questionable battle with external dns.
Any ideas on what else I would have to do. Like I'm confident enough to give it a shot but there are a ton of unknowns here and this sounds like tedious trial and error unless there is at least some guidance if any.
Beta Was this translation helpful? Give feedback.
All reactions