Hi [~weil],
Following the comments in order to clarify.
- *In the MSS the name is operator_service.yaml and not service_monitor.yaml which is the problem*. See the PR: https://github.com/integr8ly/installation/pull/841
- I understand that the operator by itself should create a service, however, we can see that it has been not happening for at least the MSS Oper master branch and that all operators are applying the service for it instead of reply in the service which should be created automatically.
- If you look here: <https://github.com/aerogear/mobile-security-service-operator/pull/163> which is a PR to upgrade the operator version for the latest one you will check that few changes were made regards to it and then the service is created there. *However, the default service created is not working for the Monitoring used in the Integr8ly which means that it still be required to be created . I mean if we use just the generated one we are not able to get the metrics as expected. *
Also, you can perform the following test:
- Install MSS oper from master and its monitoring "make install & make monitoring/install"
- Then check that all will worked fine.
- So, run `kubectl delete -f deploy/monitor/operator_service.yaml` and check that the issue is faced.
|
|
