Dustin
cd920418aa
dustin/dynk8s-provisioner/pipeline/head This commit looks good
Details
The Cluster Autoscaler does not delete the Node resource in Kubernetes after it terminates an instance: > It does not delete the Node object from Kubernetes. Cleaning up Node > objects corresponding to terminated instances is the responsibility of > the cloud node controller, which can run as part of > kube-controller-manager or cloud-controller-manager. On-premises clusters are probably not running the Cloud Controller Manager, so Node resources are liable to be left behind after a scale-down event. To keep unused Node resources from accumulating, the *dynk8s-provisioner* will now delete the Node resource associated with an EC2 instance when it receives a state-change event indicating the instance has been terminated. To identify the correct Node, it compares the value of the `providerID` field of each existing node with the instance ID mentioned in the event. An exact match is not possible, since the provider ID includes the availability zone of the instance, which is not included in the event, however, instances IDs are unique enough that this "should" never be an issue. |
||
|---|---|---|
| ci | ||
| src | ||
| terraform | ||
| tests | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| Containerfile | ||
| rustfmt.toml | ||