Problem joining in new nodes

[t-persson]

I am having a problem with joining in a new node into my cluster.

Getting this error message:
error applying new configuration: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: remote error: tls: certificate required"

I have set up my secrets, controlplane patches and worker patches according to this: https://www.talos.dev/v1.7/introduction/prodnotes/#configure-talos

The secrets.yaml was generated by talosctl when I created the cluster. The controlplane and worker yaml files have since been removed.

To generate new controlplane and worker machine configurations I do:

talosctl gen config --with-secrets secrets.yaml --config-patch-control-plane @controlplane.patch --config-patch-worker @worker.patch $(NAME) https://$(CLUSTER):$(PORT)

And I try to apply a configuration to a new node like this:
talosctl apply-config --insecure --nodes $(NODE) --file controlplane.yaml
The same error happens when adding a worker as well.

I have verified that the secrets in the controlplane.yaml and secrets.yaml are the same using talosctl gen secrets --from-controlplane-config controlplane.yaml -o test.yaml and diffing them.

# cat worker.patch
machine:
    certSANs:
        - <CLUSTER HOST>
        - 172.20.10.65

# cat controlplane.patch
machine:
    certSANs:
        - <CLUSTER HOST>
        - 172.20.10.65
    network:
        interfaces:
          - deviceSelector:
                busPath: "0*"
            dhcp: true
            vip:
                ip: 172.20.10.65
cluster:
    apiServer:
        certSANs:
            - 172.20.10.65

[smira]

This doesn't seem to be related to the way you managed the secrets, but I guess the machines you created already have the Talos machine configuration (they run with full PKI), so any --insecure commands will fail with this error.

If you have access to the console, you can check which mode the machine runs by looking at the dasbhoard

If the machines already run in non-maintenance mode, you just use your talosconfig client credentials with properly set up endpoints/nodes to manage them. E.g. you can still do talosctl apply-config to update the machine configuration.

More information on basic talosctl concepts in the documentation.

[t-persson]

Correct.

I had created a Proxmox template from a VM that was already set up before in another cluster.
Thank you for the help!