kubicctl: Error during joining of additional controlplane nodes
Hi all, hi Thorsten :-) I just tore down my kubic cluster and tried to rebuild it from scratch. Setup: - three nodes to be used as HA controlplane - separate node as kubicd and salt-master node (running on Leap 15.3, and it works!) - HAProxy on separate node (manually deployed) I could successfully initialize the cluster using:
kubicctl init --multi-master kubernetes.dmz.ojkastl.de --salt node1.dmz.ojkastl.de
But salt errors out during joining of the second node:
Jun 09 11:52:16 saltmaster kubicd[2418]: time="2021-06-09T11:52:16Z" level=info msg="Executing /usr/bin/salt: [salt node2.dmz.ojkastl.de service.enable kubelet]" Jun 09 11:52:21 saltmaster kubicd[2418]: time="2021-06-09T11:52:21Z" level=info msg="node2.dmz.ojkastl.de:\n True\n" Jun 09 11:52:21 saltmaster kubicd[2418]: time="2021-06-09T11:52:21Z" level=info msg="Executing /usr/bin/salt: [salt node2.dmz.ojkastl.de cmd.run \"kubeadm join kubernetes.dmz.ojkastl.de:6443 --token n4t9io.t1h2lb2mxtf9zs9s --discovery-token-ca-cert-hash sha256:37e925e753cd5ba399a091b3c08cac616c89baab183dbc51808bde7f0937c865 --control-plane --certificate-key [upload-certs] Using certificate key\"]" Jun 09 11:52:24 saltmaster kubicd[2418]: time="2021-06-09T11:52:24Z" level=error msg="Error invoking salt: exit status 1\nnode2.dmz.ojkastl.de:\n accepts at most 1 arg(s), received 4\n To see the stack trace of this error execute with --v=5 or higher\n"
For one thing, it did not fill in the certificate key that should be after --certificate-key (or is it just not shown in the log?). And it errors out as it apparently did not receive the right number of arguments. Am I missing some arguments in my "kubicctl node add --type master node2.dmz.ojkastl.de" command? Known issue? Should I open up a bug for that? Kind Regards Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Wed, Jun 09, Johannes Kastl wrote:
For one thing, it did not fill in the certificate key that should be after --certificate-key (or is it just not shown in the log?). And it errors out as it apparently did not receive the right number of arguments.
Am I missing some arguments in my "kubicctl node add --type master node2.dmz.ojkastl.de" command? Known issue? Should I open up a bug for that?
Looks like kubeadm changed for uploading certs or this does not work correct via salt. But I have currently no time to setup a test cluster to debug this. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)
participants (2)
-
Johannes Kastl
-
Thorsten Kukuk