-
Notifications
You must be signed in to change notification settings - Fork 228
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
Discover node features as annotations #1093
Conversation
|
✅ Deploy Preview for kubernetes-sigs-nfd ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Welcome @bebc! |
Hi @bebc. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bebc for the PR. Looks pretty good already.
In the docs we want to mention this new feature in the annotations section of get-started/introduction.md
and docs/usage/nfd-master.md
at least, I think.
Also, could you improve the commit message. Describe what is being added and e.g. how it can be used. You can take a look at the K8s commit message guidelines for some inspiration
/ok-to-test |
I meet an intractability problem.The WorkerVersionAnnotation added to the annotions in the SetLabels function(517).So the filterFeatureAnnotations function will deny it. |
Exactly. That's why we need to treat "feature annotations" from the NodeFeatureRule separately. I.e. apply the filtering to
Yeah, that would probably make sense, have "nfd annotations" and "feature annotations" as separate args to the updateNodeObject method, i.e. smth like: func (m *nfdMaster) updateNodeObject(cli *kubernetes.Clientset, nodeName string, labels Labels, nfdAnnotations, featureAnnnotations Annotations, extendedResources ExtendedResources, taints []corev1.Taint) error
Yes, there are devils in the details, a bit more than I originally imagined 😬 Big thanks for your efforts on this @bebc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bebc 👍 A few comments below, I didn't have time to check pkg/nfd-master/nfd-master.go
yet so need to do that a bit later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove all the files .idea
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bebc could you rebase the PR on top of the latest master to make it possible to review. Currently the "Files changed" shows a lot of stuff merged in other PRs
Add FeatureAnnotationsTrackingAnnotation to oldAnnotations.So that the patches can compare and restore the annotation Signed-off-by: bebc <mchf1990212@gmail.com>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1093 +/- ##
==========================================
+ Coverage 28.79% 28.95% +0.16%
==========================================
Files 51 51
Lines 7120 7145 +25
==========================================
+ Hits 2050 2069 +19
- Misses 4857 4863 +6
Partials 213 213
|
@bebc: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Rebase by doing |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi @bebc, could you rebase the PR |
return nil | ||
} | ||
|
||
// Simple and stupid re-try loop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We now have a more elegant way of running this loop, look at #1184
ping @bebc are you still working on this? If not, would you be comfortable for somebody else picking it up from here and finalizing the PR? |
Yeah, I do think that most of the work is already done. Just rebase (that will be some work) and polishing |
Rebase and updated version at #1417 |
@ArangoGutierrez: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
resolve issue #863