Open
Description
Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
Node reaper got stuck on processing a dud node that didn't exist in AWS but was still in k8s.
What you expected to happen:
We should see if we can introduce a check in node reaper to validate that the node exists in the underlying cloud-provider and if not, delete it from k8s.
How to reproduce it (as minimally and precisely as possible):
Probably remove a node from cloud provider once node reaper has scanned the nodes in k8s and trying to remove them.
Anything else we need to know?:
Environment:
- Kubernetes version:
kubectl version -o yaml
Other debugging information (if applicable):
- relevant logs:
kubectl logs <governor-pod>
Metadata
Metadata
Assignees
Labels
No labels