[caasp-beta] Problem adding additional node to cluster after 24h

[Roger Klorese]

Since we're wrapping kubeadm in CaaSP for most stuff, however, we should document it in CaaSP.

Roger B.A. Klorese
Senior Product Manager
SUSE
705 5th Ave S, Suite 1000
Seattle WA 98104
(P)+1 206.217.7432
(M)+1 425.444.5493
roger.klorese at suse.com
Schedule a meeting: https://doodle.com/RogerKlorese
GPG Key: D567 F186 A6AE D244 067E  95E4 E67D 019F 0670 D9CC

________________________________
From: caasp-beta <caasp-beta-bounces at lists.suse.com> on behalf of Thorsten Kukuk <kukuk at suse.de>
Sent: Friday, July 19, 2019 4:44 AM
To: caasp-beta at lists.suse.com
Subject: Re: [caasp-beta] Problem adding additional node to cluster after 24h

On Fri, Jul 19, roy.siek at innogy.com wrote:

> There is a hint in the kubeadm forums that the join token for kubeadm get's
> invalid after 24h

Correct, that's well documented in the kubeadm documentation and you
can list the current TTL of existing tokens with:
# kubeadm token list


  Thorsten

--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg)
_______________________________________________
caasp-beta mailing list
caasp-beta at lists.suse.com
Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/caasp-beta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20190719/39cc7998/attachment.html>