-
Notifications
You must be signed in to change notification settings - Fork 121
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
node-controller require providerID to initialize a node
Since the migration to the external cloud providers, the node controller in the cloud controller manager is responsible of initializing the nodes. There is a strong assumption across the ecosystem that the nodes has set the node.spec.providerID value, however, the node controller does not check if this value is set during the initialization of the node, and if there are some failures on the cloud provider API calls, the node can be untainted without the value and never reconciled. In addition, it seems that is possible for some cloud provider to not implement the providerID value, though is not likely this is going to happen, but for backward compatibility purposes we should allow this case. The node controller will require the providerID to untain the Nodes, except when the cloud provider does not use InstancesV2 and does implement it. ProviderID is inmutable once set, so that value has preferences, otherwise InstancesV2 is preferred over Instances. Change-Id: Ic41cf7ebcca1ff0fbd8daafc036166f19fc37251 Signed-off-by: Antonio Ojea <aojea@google.com> Kubernetes-commit: 53d38a31611c324129abd9b879d175ff388d0159
- Loading branch information
1 parent
eca6737
commit adbd099
Showing
2 changed files
with
223 additions
and
68 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
Oops, something went wrong.