-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
🐛 KCP reconcileEtcdMembers should use its own NodeRefs
These changes bring more safety when we reconcile the etcd members for the given workload cluster. To perform these changes, some modifications to the internal structs and interfaces were needed. The etcd client generator now accepts node names (as []string) instead of corev1.Node(s). This allows us to be more flexible in how we pass in the list of nodes that we expect the etcd member list to have. The reconcileEtcdMembers method already waits for all machines to have NodeRefs set before proceeding. While we check for that, now we also collect all the names in a slice before passing it in to the inner Workload struct method. A NodeRef is assigned by the Machine controller as soon as that Machine's infrastructure provider exposes the ProviderID, the machine controller then compares the ProviderID to the list of nodes available in the workload cluster, and finally assigns the NodeRef under the Machine's Status field. If a NodeRef is assigned to a Machine that KCP owns, we know it _should_ be a control plane machine even if kubeadm join hasn't set the label on the Node object. Signed-off-by: Vince Prignano <[email protected]>
- Loading branch information
Showing
8 changed files
with
66 additions
and
62 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters