-
Notifications
You must be signed in to change notification settings - Fork 219
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
MGMT-9272 Automatic agent classification labels #3721
MGMT-9272 Automatic agent classification labels #3721
Conversation
This CRD defines the API for users to classify Agents by providing a query that is run on the Agent's inventory along with a corresponding label.
The AgentLabel controller updates Agents' labels according to defined AgentClassification CRs in the same namespace. The AgentClassification controller maintain counts for each AgentClassification of how many Agents matched and how many had errors when trying to match. It also has a finalizer such that the AgentClassification won't be deleted as long as there are Agents matching it.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: avishayt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
@@ Coverage Diff @@
## master #3721 +/- ##
========================================
Coverage 65.90% 65.91%
========================================
Files 175 178 +3
Lines 24732 25066 +334
========================================
+ Hits 16300 16522 +222
- Misses 6831 6924 +93
- Partials 1601 1620 +19
|
Can you outline the differences from the previous PR, if any? |
No differences. Rebased with no conflicts. |
/lgtm |
This ensures that: 1. Specified labels are valid and do not change 2. The specified query can be parsed
3bd6431
to
43080ea
Compare
/lgtm |
/test e2e-metal-assisted |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
Waiting for openshift/assisted-test-infra#1633 |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@avishayt: The following test failed, say
Full PR test history. Your PR dashboard. 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. |
* MGMT-9272: Define AgentClassification CRD This CRD defines the API for users to classify Agents by providing a query that is run on the Agent's inventory along with a corresponding label. * MGMT-9272: AgentClassification and AgentLabel controllers The AgentLabel controller updates Agents' labels according to defined AgentClassification CRs in the same namespace. The AgentClassification controller maintain counts for each AgentClassification of how many Agents matched and how many had errors when trying to match. It also has a finalizer such that the AgentClassification won't be deleted as long as there are Agents matching it. * MGMT-9272: AgentClassification admission hooks This ensures that: 1. Specified labels are valid and do not change 2. The specified query can be parsed * MGMT-9272: AgentClassification documentation * MGMT-9272: go.mod and go.sum * MGMT-9272: Agent labels subsystem test
* MGMT-9272: Define AgentClassification CRD This CRD defines the API for users to classify Agents by providing a query that is run on the Agent's inventory along with a corresponding label. * MGMT-9272: AgentClassification and AgentLabel controllers The AgentLabel controller updates Agents' labels according to defined AgentClassification CRs in the same namespace. The AgentClassification controller maintain counts for each AgentClassification of how many Agents matched and how many had errors when trying to match. It also has a finalizer such that the AgentClassification won't be deleted as long as there are Agents matching it. * MGMT-9272: AgentClassification admission hooks This ensures that: 1. Specified labels are valid and do not change 2. The specified query can be parsed * MGMT-9272: AgentClassification documentation * MGMT-9272: go.mod and go.sum * MGMT-9272: Agent labels subsystem test
Resubmitting this PR which was reverted due to this bug which has now been fixed.
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Assignees
/assign @filanov
/assign @nmagnezi
/assign @omertuc
Checklist
docs
, README, etc)Reviewers Checklist