Kubernetes Bootstrap - error executing bootstrap: rpc error: code = Unavailable desc = name resolver error: produced zero addresses #4946

Sparkxxx · 2022-02-09T04:31:10Z

Sparkxxx
Feb 9, 2022

talosctl gen config "k8s-talos-1" "https://k8s-ctrlplane.kub.local:6443"

I am trying to use vip ( 10.170.0.20 - k8s-ctrlplane.kub.local ) and alocate IPs trough dhcp for each node based on mac addresses (no dns name for controlplane nodes as per docs). https://k8s-ctrlplane.kub.local:6443 is also the cluster endpoint, 10.170.0.11,12,13 are the controlplane nodes.
When trying to bootstrap I get:

talosctl --talosconfig=./talosconfig bootstrap --nodes 10.170.0.11
error executing bootstrap: rpc error: code = Unavailable desc = name resolver error: produced zero addresses

talosconfig:

context: k8s-talos-1
contexts:
    k8s-talos-1:
        endpoints:
            - 10.170.0.11,10.170.0.12,10.170.0.13
        nodes:
            - 10.170.0.11
        ca: ...
        crt: ... 
        key: ...

controlplane.yml for all 3 nodes:

    network:
      interfaces:
        - interface: eth0
          dhcp: true
          vip:
            ip: 10.170.0.20

talosctl edit mc --nodes 10.170.0.11
rpc error: code = Unavailable desc = name resolver error: produced zero addresses

I think it's expecting to resolve the ip to dns but at this point there is no vip available (it should be up after kubernetes etcd bootstrap) so, on purpose, there should be no dns names asociated with the cluster yet.
Would you be so kind to direct me in this matter?
thx

Answered by sergelogvinov

Feb 9, 2022

I think, this is yaml format issue.
Try this

context: k8s-talos-1
contexts:
    k8s-talos-1:
        endpoints:
            - 10.170.0.11
            - 10.170.0.12
            - 10.170.0.13
...

View full answer

sergelogvinov · 2022-02-09T07:21:35Z

sergelogvinov
Feb 9, 2022
Sponsor

I think, this is yaml format issue.
Try this

context: k8s-talos-1
contexts:
    k8s-talos-1:
        endpoints:
            - 10.170.0.11
            - 10.170.0.12
            - 10.170.0.13
...

0 replies

Sparkxxx · 2022-02-09T09:16:07Z

Sparkxxx
Feb 9, 2022
Author

Edited but no change,
I'll post here all the commands I went through and now looking back I might have abused it a little?

passing _apply-config --insecure --nodes 10.170.0.11,10.170.0.12,10.170.0.13_ <<--- didn't complained  
passing _apply-config --insecure --nodes 10.170.0.11 10.170.0.12 10.170.0.13 --file controlplane.yaml_ <<--- issued the error _accepts at most 1 arg(s), received 2_

so my conclusion is that applying config should be done individually on each node, although from bellow I think .12 got something?

This is also interesting

sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.12 --file controlplane.yaml
error applying new configuration: rpc error: code = Unavailable desc = connection closed before server preface received

sparkx@k8s-devops-0-10:~$ cd k8s-cluster/
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl gen config "k8s-talos-1" "https://k8s-ctrlplane.kub.local:6443"
generating PKI and tokens
created /home/sparkx/k8s-cluster/controlplane.yaml
created /home/sparkx/k8s-cluster/worker.yaml
created /home/sparkx/k8s-cluster/talosconfig
sparkx@k8s-devops-0-10:~/k8s-cluster$ ls -al
total 140
drwxrwxr-x  2 sparkx sparkx  4096 Feb  8 19:48 .
drwxr-x--- 13 sparkx sparkx  4096 Feb  8 18:01 ..
-rw-rw-r--  1 sparkx sparkx 82107 Nov 19 09:43 completion.bash.inc
-rw-r--r--  1 sparkx sparkx 21212 Feb  8 19:51 controlplane.yaml
-rw-r--r--  1 sparkx sparkx  1608 Feb  8 19:48 talosconfig
-rw-r--r--  1 sparkx sparkx 19412 Feb  8 19:48 worker.yaml
sparkx@k8s-devops-0-10:~/k8s-cluster$ mv worker.yaml wrkr-1.yaml
sparkx@k8s-devops-0-10:~/k8s-cluster$ cp wrkr-1.yaml wrkr-2.yaml

sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.11,10.170.0.12,10.170.0.13 --file controlplane.yaml
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.14 --file wrkr-1.yaml
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig config endpoint 10.170.0.11 10.170.0.12 10.170.0.13
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig config endpoint 10.170.0.11
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.15 --file wrkr-2.yaml
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl bootstrap --nodes 10.170.0.11
error constructing client: failed to determine endpoints

Changing tactics

sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.11 10.170.0.12 10.170.0.13 --file controlplane.yaml
accepts at most 1 arg(s), received 2
...
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.11 --file controlplane.yaml
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.12 --file controlplane.yaml
error applying new configuration: rpc error: code = Unavailable desc = connection closed before server preface received
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.12 --file controlplane.yaml
error applying new configuration: rpc error: code = Unavailable desc = connection closed before server preface received
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.13 --file controlplane.yaml
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl apply-config --insecure --nodes 10.170.0.12 --file controlplane.yaml
error applying new configuration: rpc error: code = Unavailable desc = connection closed before server preface received
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl bootstrap --nodes 10.170.0.11
error constructing client: failed to determine endpoints
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl bootstrap --nodes 10.170.0.12
error constructing client: failed to determine endpoints
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig config endpoint 10.170.0.11
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig config endpoint 10.170.0.11 10.170.0.12 10.170.0.13
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl bootstrap --nodes 10.170.0.11
error constructing client: failed to determine endpoints

sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig config endpoint 10.170.0.11 10.170.0.12 10.170.0.13
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig config node 10.170.0.11
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl bootstrap --nodes 10.170.0.11
error constructing client: failed to determine endpoints
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig config endpoint 10.170.0.11,10.170.0.12,10.170.0.13
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig config node 10.170.0.11
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl bootstrap --nodes 10.170.0.11
error constructing client: failed to determine endpoints
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig \
    --nodes 10.170.0.11 version
Client:
        Tag:         v0.14.1
        SHA:         7182bcf2
        Built:
        Go version:  go1.17.5
        OS/Arch:     linux/amd64
Server:
error getting version: rpc error: code = Unavailable desc = name resolver error: produced zero addresses
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl --talosconfig=./talosconfig     --nodes 10.170.0.12 version
Client:
        Tag:         v0.14.1
        SHA:         7182bcf2
        Built:
        Go version:  go1.17.5
        OS/Arch:     linux/amd64
Server:
error getting version: rpc error: code = Unavailable desc = name resolver error: produced zero addresses
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl config merge ./talosconfig
sparkx@k8s-devops-0-10:~/k8s-cluster$ talosctl bootstrap --nodes 10.170.0.11
error executing bootstrap: rpc error: code = Unavailable desc = name resolver error: produced zero addresses

Should I scarap it and restart, would you like to investigate further?

6 replies

Sparkxxx Feb 9, 2022
Author

sparkx@k8s-devops-0-10:~$ cat ./talosconfig

context: ""
contexts: {}

sparkx@k8s-devops-0-10:~$ talosctl --talosconfig=./talosconfig config contexts

CURRENT   NAME   ENDPOINTS   NODES
sparkx@k8s-devops-0-10:~$

smira Feb 9, 2022
Maintainer

so I'm confused here, your talosconfig is empty, that won't work. Usually talosconfig is generated by talosctl gen config.

You can merge it to the default location with talosctl config merge talosconfig or keep it in a separate file.

In any case the only thing you need to do usually is to set the endpoints.

Sparkxxx Feb 9, 2022
Author

How can I reset the machines to original state to try again so that I won't have to recreate them?

smira Feb 9, 2022
Maintainer

It really depends on the infrastructure you're using.

With bare metal, if the Talos API is unavailable, for 0.14 there's no option rather than booting some other OS and doing wipefs on the block device. Basically block device should be wiped.

Sparkxxx Feb 9, 2022
Author

I'm on Proxmox, deleted the drive and added a new one for each vm, thx

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Kubernetes Bootstrap - error executing bootstrap: rpc error: code = Unavailable desc = name resolver error: produced zero addresses #4946

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 6 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Kubernetes Bootstrap - error executing bootstrap: rpc error: code = Unavailable desc = name resolver error: produced zero addresses #4946

Sparkxxx Feb 9, 2022

Replies: 2 comments · 6 replies

sergelogvinov Feb 9, 2022 Sponsor

Sparkxxx Feb 9, 2022 Author

Sparkxxx Feb 9, 2022 Author

smira Feb 9, 2022 Maintainer

Sparkxxx Feb 9, 2022 Author

smira Feb 9, 2022 Maintainer

Sparkxxx Feb 9, 2022 Author

Sparkxxx
Feb 9, 2022

Replies: 2 comments 6 replies

sergelogvinov
Feb 9, 2022
Sponsor

Sparkxxx
Feb 9, 2022
Author

Sparkxxx Feb 9, 2022
Author

smira Feb 9, 2022
Maintainer

Sparkxxx Feb 9, 2022
Author

smira Feb 9, 2022
Maintainer

Sparkxxx Feb 9, 2022
Author