-
Notifications
You must be signed in to change notification settings - Fork 13
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
[COST-5027] opt-in per namespace ROS OCP recommendations #355
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #355 +/- ##
==========================================
+ Coverage 85.85% 86.31% +0.45%
==========================================
Files 13 13
Lines 2171 2206 +35
==========================================
+ Hits 1864 1904 +40
+ Misses 224 220 -4
+ Partials 83 82 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
kube_namespace_labels{label_insights_cost_management_optimizations='true', namespace!~'kube-.*|openshift|openshift-.*'}
which will filter the results based on this labelExample report where
costmanagement-metrics-operator
is the only namespace with the enabled label.ros-openshift-202405.csv
Testing:
(using a cluster. can request one from ClusterBot with
launch 4.15 aws,single-node
)This will create a CR that only collects the most recent hour of data. If using a ClusterBot cluster, there likely won't be any data to collect during the first reconciliation anyway.
4. Wait until the operator generates its first report.
5. Apply the following label:
(If this pod does not mount to the volume, update the
node
in the yaml to match the operator node)Notice that there is no
ros-openshift-202405.csv
file intmp/data
.7. Examine the CR and see the data collection message:
ros-openshift-202405.csv
file intmp/data
which contains line items only for thekoku-metrics-operator
namespace.