-
Notifications
You must be signed in to change notification settings - Fork 39
Removing LastTransitionTime from the NMC status.
#1066
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
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ybettan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-kmm ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1066 +/- ##
==========================================
- Coverage 79.09% 74.40% -4.70%
==========================================
Files 51 77 +26
Lines 5109 6880 +1771
==========================================
+ Hits 4041 5119 +1078
- Misses 882 1549 +667
- Partials 186 212 +26 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Github runners are being under maintenance - hopefully, CI will be working again soon. |
Since we are now checking if a node has rebooted using the node's `status.nodeInfo.bootID` then we don't need to compare the node's ready time and the NMC last recorded node ready time anymore. Signed-off-by: Yoni Bettan <[email protected]>
|
/lgtm |
|
/unhold |
Since we are now checking if a node has rebooted using the node's
status.nodeInfo.bootIDthen we don't need to compare the node's readytime and the NMC last recorded node ready time anymore.
/assign @yevgeny-shnaidman (only the last commit is relevant)
/hold
It should only be merged after #1061
I have tested the upgrade flow and I didn't inspect an issue during the upgrade.