h4. What
* The operator needs to monitor/watch all namespace with some label/tag in order to do actions
* When a new To attend the definition "operators to call the endpoint to create the app be tagged with on bind/unbind." will watch all namespaces and filter by the respective MDC criteria every time and for each project/namespace returned it will check if the namespace has the label /MSS criteria(I mean if the operator need project is bind or not to the MSS).
* IF YES: " call the endpoint to create the app on bind " binding of (If the REST app is not already created the Service will create it)
* IF NOT: " call the endpoint to unbind the app" (If the app exist in the Service it means that should be disabled)
h4. Why
* To create do the binding / unbinding process of apps
* When the operator finds out a deployment with a label it should do the bidding process
*NOTES:*
* The operator is watching all the namespaces of the cluster. See [here|https://github.com/aerogear/mobile-security-service-operator/blob/master/cmd/manager/main.go#L78]
* Shows that the Prometheus do something similar. Check it [here|https://github.com/coreos/prometheus-operator]
* Check the documentation over how the MDC will work in OCP4 and with the operators: https://docs.google.com/document/d/1KwE5rVfj9L2gnzNGL1TTYVvoyNgBw61XIiN3eCNg1b4/edit
* Definitions and ML discussion: http://post-office.corp.redhat.com/archives/mobile-customer-success/2019-March/msg00052.html
* Shows that the Prometheus do something similar. Check it [here|https://github.com/coreos/prometheus-operator]
|
|
