Intro
Currently, each node that joins the cluster registers with the registration service, which sends an ignition with a UUID for that machine and creates a new TEC machine that represents this machine in the cluster. There is no mapping between the TEC machine that the registration service creates and the k8s node.
One problem with this is that when a node gets deleted, the TEC machine still lives on.
Solution proposal
One option is to bind after boot. The operator detects (using a reconciliation loop) that a new node is created and boots up. The UUID that was generated by the registration service exists on the node (trustee pin uses this UUID at boot time). After the node boots, the operator reads the UUID and binds that node with the matching TEC machine.
Intro
Currently, each node that joins the cluster registers with the registration service, which sends an ignition with a UUID for that machine and creates a new TEC machine that represents this machine in the cluster. There is no mapping between the TEC machine that the registration service creates and the k8s node.
One problem with this is that when a node gets deleted, the TEC machine still lives on.
Solution proposal
One option is to bind after boot. The operator detects (using a reconciliation loop) that a new node is created and boots up. The UUID that was generated by the registration service exists on the node (trustee pin uses this UUID at boot time). After the node boots, the operator reads the UUID and binds that node with the matching TEC machine.