This message was deleted.
# k3da
adamant-kite-43734
02/10/2023, 7:01 PMThis message was deleted.
f
future-vase-71145
02/14/2023, 8:13 PM@wide-garage-9465 pinging you because I see you responding to other questions here (sorry if that's not ok). Any suggestions? Looks like this isn't actually working (it keeps getting reverted) and I may need to go back to 4.4.6.
w
wide-garage-9465
02/14/2023, 8:19 PMIs that actually a patch that you're deploying there?
wide-garage-9465
02/14/2023, 8:20 PMWould you get along with the coredns-custom configmap?
f
future-vase-71145
02/14/2023, 8:21 PMI tried the
coredns-customfuture-vase-71145
02/14/2023, 8:22 PMAnd yes, I'm using an actual patch. The contents of that patch file are:
Copy code
data:
Corefile: |
.:53 {
errors
health
ready
rewrite name regex (.*).<http://local.example.com|local.example.com> public-nginx-ingress-nginx-controller.default.svc.cluster.local
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
fallthrough in-addr.arpa ip6.arpa
}
hosts /etc/coredns/NodeHosts {
ttl 60
reload 15s
fallthrough
}
prometheus :9153
forward . /etc/resolv.conf
cache 30
loop
reload
loadbalance
}future-vase-71145
02/14/2023, 8:23 PMI just copied the default and added my rewrite rule
future-vase-71145
02/14/2023, 8:24 PMI'm new to dealing with coredns and I've never managed dns zone files, so it's entirely possible I'm missing something simple.
w
wide-garage-9465
02/14/2023, 8:26 PMOK.
k3d is now also overwriting K3s' default CoreDNS file. It was meant as a temporary solution until coredns-custom was ready, but it wasn't removed yet.
I could imagine (though I don't know how), that it interferes with your solution here.
With the coredns-custom configmap you can add another zone for .example.com, which would be separate from the root zone (.:53)
f
future-vase-71145
02/14/2023, 8:27 PMI think I tried that, but I tried enough things that I can't remember for sure. 🙃 I'll try it again.
w
wide-garage-9465
02/14/2023, 8:29 PMwide-garage-9465
02/14/2023, 8:30 PMwide-garage-9465
02/14/2023, 8:30 PMHope that helps 🙂
wide-garage-9465
02/14/2023, 8:30 PMI have to get into this topic again 😬
f
future-vase-71145
02/14/2023, 8:32 PM Copy code
apiVersion: v1
kind: ConfigMap
metadata:
name: coredns-custom
namespace: kube-system
data:
example.server: |
.<http://example.com|example.com> {
rewrite name regex (.*).<http://local.example.com|local.example.com> public-nginx-ingress-nginx-controller.default.svc.cluster.local
}future-vase-71145
02/14/2023, 8:32 PMI think this is what should work then?
w
wide-garage-9465
02/14/2023, 8:33 PMYup, I guess/hope so
f
future-vase-71145
02/14/2023, 8:33 PMok, gonna try that 🤞
w
wide-garage-9465
02/14/2023, 8:33 PMNot sure if any additional configuration is needed then
f
future-vase-71145
02/14/2023, 10:05 PMSo far no luck 😞
future-vase-71145
02/14/2023, 11:49 PMFinally got it. I'm using a config file for k3d and I was setting
image Copy code
apiVersion: v1
kind: ConfigMap
metadata:
name: coredns-custom
namespace: kube-system
data:
local.server: |
<http://local.example.com|local.example.com> {
rewrite name regex (.*).<http://local.example.com|local.example.com> public-nginx-ingress-nginx-controller.default.svc.cluster.local
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
fallthrough in-addr.arpa ip6.arpa
}
}future-vase-71145
02/14/2023, 11:53 PMThanks for the pointers. I'd seen the github thread, but that blog post was really helpful for testing.
w
wide-garage-9465
02/15/2023, 6:19 AMGreat! Glad that you got it working :)
37 Views