-
Notifications
You must be signed in to change notification settings - Fork 14
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
Gh 668 #143
Gh 668 #143
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #143 +/- ##
==========================================
- Coverage 85.01% 84.40% -0.61%
==========================================
Files 19 19
Lines 994 994
==========================================
- Hits 845 839 -6
- Misses 97 100 +3
- Partials 52 55 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This change is needed as the limitador operator typically runs in the same namespace as other operators when deployed as part of kuadrant. |
@eguzki thoughts on this change? |
Hey @eguzki, What do you think of these changes am I missing anything? |
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.
Overall looks good.
One question regarding the labels left.
@david-martin yes, it is sufficient to make the changes here so that kuadrant-operator deploys the resources with the new label
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.
Other than a tiny issue with the createdAt
field, LGTM. But it needs rebase first before approval
6befa9c
to
c07e895
Compare
WHAT:
Adding labels to resources as limitador often runs in the same namespace as other operators so we are seeing certain issues with metrics repeating mainly around the service resource. Since its adding a label it shouldn't break things