Kubernetes

1057 readers

1 users here now

founded 2 years ago

MODERATORS

[email protected]

How to get kubernetes to add all its internal dns entries to your own dns server (lemmy.zip)

submitted 1 week ago by [email protected] to c/[email protected]

22 comments fedilink hide all child comments

By this I mean, I have a powerdns server running in my cluster, I would like Kubernetes to add/update dns entries in my dns server to reflect all services or any domains that would be used within the cluster, this is to fix a current issue I am having, and for general control and centralization purposes.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 week ago (1 children)

Sorry - I totally misread this. You cannot access internet addresses. So it's a routing or NAT issue, most likely.

I assume you are using k3d for this, btw?

So.. on the "server" (eg. docker exec -ti k3d-k3s-default-server-0 -- /bin/sh), you should be able to "ping 8.8.8.8" successfully.

If not, the issue may lie with your host's docker setup.

[–] [email protected] 1 points 1 week ago (1 children)

Not k3d, just plain k3s

[–] [email protected] 1 points 1 week ago (1 children)

Your k3s/calico networking is likely screwed. Try creating a new cluster with flannel instead.

[–] [email protected] 1 points 1 week ago (1 children)

Well I switched to cilium, same issue, and the reason I started using a CNI earlier than I intended was because flannel didn't work.

This issue might seem complex but could you tell me some debugging stuff and logs to try to maybe get to the source of the issue or atleast provide a way to reproduce my issue (so I could maybe file a bug report)

[–] [email protected] 1 points 1 week ago

It might be a simple issue like ip forwarding not being enabled, or host-level iptables configuration, or perhaps weird and wonderful routing (eg. wireguard or other VPNs).