kubernetes-sigs/cluster-api

Speed up provisioning of the first set of worker machines by improving predicates on cluster watch

Open

#8,835 opened on Jun 12, 2023

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (1,532 forks)auto 404
area/bootstraphelp wantedkind/featurepriority/important-longtermtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

What would you like to be added (User Story)?

As a users I want CAPI to provision machines as fast as possible

Detailed Description

While looking at cluster provisioning I noticed that the kubeadm bootstrap controller takes time to react to when the cluster reports control plane ready, which is the moment when workers machines are allowed to join.

From a preliminary investigation, the kubeadm bootstrap controller is watching for clusters, but existing predicates (more specifically predicates.ClusterUnpausedAndInfrastructureReady) are filtering out events when the cluster transition to control plane ready.

This issue is about investigating if we can speed up provisioning of the first set of worker machines by improving predicates

Anything else you would like to add?

Note predicates.ClusterUnpausedAndInfrastructureReady, so some research is required before changing this method, or most probably it is better to create a new one.

Label(s) to be applied

/kind feature /area bootstrap

Contributor guide