Skip to content

Conversation

@asm582
Copy link
Member

@asm582 asm582 commented Aug 9, 2022

Solves #202

@asm582 asm582 requested a review from dmatch01 August 9, 2022 18:47
@dmatch01
Copy link
Collaborator

@asm582 See comments from slack.

@asm582
Copy link
Member Author

asm582 commented Aug 15, 2022

@dmatch01 Thanks for the review, fixed the bug. Now the code loops through all the conditions and retrieves the status of the Ready condition type.

Copy link
Collaborator

@dmatch01 dmatch01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see suggested changes. Also please add a comment in the updated PR to include the testcase(s) run for this PR. Should be something similar to verifying calculations updates after a node is marked as not ready but still schedulable. k drain might be helpful here or even a deletion of the kubelet process (if you have access to the node and can safely restart the kubelet).

@asm582 asm582 closed this by deleting the head repository Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants