Skip to content

fix(coredns): dns resolution fix#102

Merged
stevensbkang merged 8 commits intodevelopfrom
fix/ks-21/stablise-coredns
Feb 23, 2026
Merged

fix(coredns): dns resolution fix#102
stevensbkang merged 8 commits intodevelopfrom
fix/ks-21/stablise-coredns

Conversation

@stevensbkang
Copy link
Member

No description provided.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR implements DNS resolution improvements for the kubesolo Kubernetes distribution. The changes ensure that CoreDNS can properly resolve external DNS queries by using valid upstream nameservers, fixing potential issues in environments where the host's /etc/resolv.conf contains loopback or link-local addresses.

Changes:

  • Updated kubelet to use a validated or auto-generated resolv.conf for container DNS resolution
  • Added DNS policy and wait logic for CoreDNS pod readiness
  • Improved CoreDNS configuration with loop detection and updated forwarding and caching behavior

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
internal/runtime/network/ip.go Added GetHostResolvConf function to find or generate a valid resolv.conf with global unicast nameservers, following k3s approach
pkg/kubernetes/kubelet/config.go Changed kubelet to use GetHostResolvConf instead of hardcoded /etc/resolv.conf path
pkg/components/coredns/deployment.go Added DNSPolicy: DNSDefault to CoreDNS pod spec to use node's DNS configuration
pkg/components/coredns/coredns.go Added waitForCoreDNSReady function to ensure CoreDNS is ready before returning from Deploy
pkg/components/coredns/configuration.go Updated CoreDNS Corefile: added loop detection, changed forward to use /etc/resolv.conf, enabled caching for cluster.local success responses, reordered plugins

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@stevensbkang stevensbkang changed the title fix(coredns): potential dns resolution fix fix(coredns): dns resolution fix Feb 19, 2026
@stevensbkang stevensbkang merged commit 1397537 into develop Feb 23, 2026
4 checks passed
@stevensbkang stevensbkang deleted the fix/ks-21/stablise-coredns branch February 23, 2026 21:56
stevensbkang added a commit that referenced this pull request Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants