[KOGITO-2960] - Prometheus integration with kogito-cloud-operator #521
Conversation
/jenkins test |
Codecov Report
@@ Coverage Diff @@
## master #521 +/- ##
==========================================
- Coverage 42.01% 37.60% -4.41%
==========================================
Files 169 162 -7
Lines 9012 7933 -1079
==========================================
- Hits 3786 2983 -803
+ Misses 4812 4602 -210
+ Partials 414 348 -66
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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 Jain! Looks good, I'm just curious about this "custom_writer/reader" that you created, mimicking what we already have on client
package, but with this swtich case to verify if it's a Prometheus object or not. Why we need it? I believe we can think on something different to reuse the existing functions.
EDIT: I'm not seeing an update in the openapi generated file. Can you please confirm that you executed the openapi binary? Also, were you able to test this integration with the Prometheus Operator on minikube/crc?
...og/kogito-operator/1.0.0-snapshot/kogito-operator.v1.0.0-snapshot.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
deploy/olm-catalog/kogito-operator/manifests/kogito-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
/jenkins test |
Change detected in the PR, requesting reviews and running pipeline(if required) again |
/jenkins test |
Change detected in the PR, requesting reviews and running pipeline(if required) again |
/jenkins test |
1 similar comment
/jenkins test |
@ricardozanini
Code is written to work with controller client only that why I had written custom reader/writer object which receive complete
Following auto-generated files are included in change list :
I tried it on OC cluster. This PR has successfully generates |
/jenkins test |
Change detected in the PR, requesting reviews and running pipeline(if required) again |
/jenkins test |
Hi! My point is that this interface of "custom resources" that you created is basically this: https://github.com/kiegroup/kogito-cloud-operator/blob/master/pkg/client/kubernetes/resource.go Excepts that you are adding a condition of "if is prometheus resource". I'm suggesting to change this to have one interface doing the wrapper around the client that is smart enough to handle Prometheus resources as well. |
deploy/olm-catalog/kogito-operator/manifests/kogito-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
@spolti @sutaakar @Kaitou786 could you guys please take a look in this PR? |
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.
approving, but left a comment about the flags used.
[KOGITO-2960] - Incorporate review comments [KOGITO-2960] - Incorporate review comments [KOGITO-2960] - Incorporate review comments [KOGITO-2960] - Incorporate review comments [KOGITO-2960] - Incorporate review comments
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.
@vaibhavjainwiz I'm assuming you're going to update the "prometheus" name from the public interface to "monitoring" instead, right?
Change detected in the PR, requesting reviews and running pipeline(if required) again |
yes..already done |
Change detected in the PR, requesting reviews and running pipeline(if required) again |
Change detected in the PR, requesting reviews and running pipeline(if required) again |
Jira issue : https://issues.redhat.com/browse/KOGITO-2960
Many thanks for submiting your Pull Request ❤️!
Please make sure that your PR meets the following requirements:
[KOGITO-XYZ] Subject