Skip to content

Registry reachable in cluster#71

Merged
alicefr merged 2 commits into
bootc-dev:mainfrom
alicefr:registry-reachable-in-cluster
Jun 24, 2026
Merged

Registry reachable in cluster#71
alicefr merged 2 commits into
bootc-dev:mainfrom
alicefr:registry-reachable-in-cluster

Conversation

@alicefr

@alicefr alicefr commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator

Enable CoreDNS fallthrough so that unresolved cluster.local queries (e.g. registry.cluster.local) are forwarded to the node's /etc/resolv.conf, which reaches the bink DNS container. This allows pods to resolve bink-managed DNS names like the local registry

Fixes: #70

alicefr added 2 commits June 24, 2026 14:33
Pods inside a bink cluster cannot resolve bink-managed DNS names
like registry.cluster.local because CoreDNS's kubernetes plugin
handles the cluster.local zone but only resolves Kubernetes
services/pods/endpoints.

After kubeadm deploys CoreDNS, patch the Corefile to change
"fallthrough in-addr.arpa ip6.arpa" to just "fallthrough". This
removes the zone restriction so all unresolved cluster.local
queries (not just reverse DNS) fall through to the forward plugin,
which reaches the bink dnsmasq container via the node's
/etc/resolv.conf.

Fixes: bootc-dev#70

Assisted-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Alice Frosi <afrosi@redhat.com>
Runs nslookup from the busybox pod to verify CoreDNS fallthrough
resolves bink-managed DNS names inside the cluster.

Assisted-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Alice Frosi <afrosi@redhat.com>
@alicefr

alicefr commented Jun 24, 2026

Copy link
Copy Markdown
Collaborator Author

@Johan-Liebert1 PTAL

@alicefr alicefr merged commit 990a6a6 into bootc-dev:main Jun 24, 2026
6 checks passed
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.

The local registry cannot be solved by a workload running in the cluster

2 participants