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

Node cannot join the cluster due to expired bootstrap token #772

Closed
schrodit opened this issue Jan 27, 2023 · 0 comments · Fixed by #773
Closed

Node cannot join the cluster due to expired bootstrap token #772

schrodit opened this issue Jan 27, 2023 · 0 comments · Fixed by #773
Labels
kind/bug Bug priority/3 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)

Comments

@schrodit
Copy link
Contributor

How to categorize this issue?

/kind bug
/priority 3

What happened:
Mostly always my machines take more than 20 minutes to be created in the cloudprovider.
Therefore the workers are configured to with a specific machineCreationTimeout of 50m.
When the nodes come up after approx. 30min the node is unable to join cluster due to a expired bootstrap token.

What you expected to happen:

Bootstrap token for node does not expired before the configured spec.worker[].machineController.machineCreationTimeout

How to reproduce it (as minimally and precisely as possible):

  1. Create a shoot and configure a worker group with a machineCreationTimeout of more than 20m
  2. let the machine need more than 20 minutes to be created

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): 1.22.17
  • Cloud provider or hardware configuration: Equinix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Bug priority/3 Priority (lower number equals higher priority) status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants