-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node deletion #127
node deletion #127
Conversation
Codecov Report
@@ Coverage Diff @@
## master #127 +/- ##
==========================================
- Coverage 70.05% 69.71% -0.34%
==========================================
Files 12 12
Lines 1259 1311 +52
==========================================
+ Hits 882 914 +32
- Misses 310 325 +15
- Partials 67 72 +5
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
why we need to delete the node in lifecyle manager explicitely? |
Because the node IPs are reused by the cloud providers. When a new node joins the cluster with a previously allocated IP, it will fetch the same object which has previous role and labels. Because of this the node is never able to join the cluster and will be stuck in |
|
Signed-off-by: sbadiger <shreyas_badiger@intuit.com>
Signed-off-by: sbadiger <shreyas_badiger@intuit.com>
node IPs are reused by the cloud providers. When a new node joins the cluster with a previously allocated IP, it will fetch the same object which has a previous role and labels. Because of this the node is never able to join the cluster and will be stuck in
NotReady
state. Therefore, once the node is drained, we can safely delete the node.