Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add host dns support for resolving member addrs #8610

Merged
merged 1 commit into from
Apr 18, 2024

Conversation

DmitriyMV
Copy link
Member

Closes #8330

@DmitriyMV
Copy link
Member Author

DmitriyMV commented Apr 18, 2024

Okay, I went this way:

> sudo -E talosctl cluster create \ 
--provisioner=qemu \
--cidr=172.20.0.0/24 \
...
--controlplanes 1 \
--workers 1 \
--config-patch=@./patch.yaml

With patch.yaml being

version: v1alpha1
machine:
    features:
        hostDNS:
            enabled: true
            forwardKubeDNSToHost: true
            resolveMemberNames: true

Then

> kubectl run alpine --image alpine -it -- ash

Then

> ping talos-default-controlplane-1

And result is:
image

🎉

internal/pkg/dns/dns.go Outdated Show resolved Hide resolved
internal/pkg/dns/dns.go Outdated Show resolved Hide resolved
Closes siderolabs#8330

Signed-off-by: Dmitriy Matrenichev <dmitry.matrenichev@siderolabs.com>
@DmitriyMV
Copy link
Member Author

/m

@talos-bot talos-bot merged commit 908f67f into siderolabs:main Apr 18, 2024
18 checks passed
@DmitriyMV DmitriyMV deleted the node-dns branch April 18, 2024 13:07
@smira smira mentioned this pull request Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backported
Development

Successfully merging this pull request may close these issues.

resolve machine hostnames (from discovery) via local DNS resolver
3 participants