-
Notifications
You must be signed in to change notification settings - Fork 245
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
nfd-master: Add status for NodeFeatureRule CRD #1901
base: master
Are you sure you want to change the base?
Conversation
Hi @ozhuraki. 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-sigs/prow repository. |
✅ Deploy Preview for kubernetes-sigs-nfd ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
0573dbb
to
09c8ef0
Compare
Thanks for the input. Take a look, please if this would address extra updates? |
/assign @marquiz |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ozhuraki The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Oleg Zhurakivskyy <oleg.zhurakivskyy@intel.com>
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-sigs/prow repository. |
@@ -131,6 +131,8 @@ type NodeFeatureRule struct { | |||
|
|||
// Spec defines the rules to be evaluated. | |||
Spec NodeFeatureRuleSpec `json:"spec"` | |||
// +optional | |||
Status NodeFeatureRuleStatus `json:"status"` |
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.
Status NodeFeatureRuleStatus `json:"status"` | |
Status NodeFeatureRuleStatus `json:"status,omitempty"` |
metav1.TypeMeta `json:",inline"` | ||
metav1.ObjectMeta `json:"metadata,omitempty"` |
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 don’t need to include metadata in the Status, as it doesn't add any additional value there.
metav1.ObjectMeta `json:"metadata,omitempty"` | ||
|
||
// +optional | ||
Rules []RuleStatus `json:"rules"` |
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.
Rules []RuleStatus `json:"rules"` | |
Rules []RuleStatus `json:"rules,omitempty"` |
// +k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object | ||
// +genclient |
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.
These markers were replaced by kubebuilder:object:root=true
. So, we could drop this off too. Reference: https://book.kubebuilder.io/migration/legacy/migration_guide_v1tov2.html?highlight=genclient#migrate-the-apis
// +kubebuilder:resource:scope=Namespaced,shortName=nfs | ||
// +kubebuilder:subresource:status |
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.
These should be organized under the parent object NodeFeatureRule. Since they already exist, you could just drop them. You can find the relevant section here:
// +kubebuilder:object:root=true |
Closes: #1072