Skip to content
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.

Allow for alternative monitoring solutions #172

Open
arthurdm opened this issue Oct 29, 2019 · 0 comments
Open

Allow for alternative monitoring solutions #172

arthurdm opened this issue Oct 29, 2019 · 0 comments
Labels

Comments

@arthurdm
Copy link
Member

Currently the monitoring key in our CRD is specific to Prometheus' ServiceMonitor. As k8s / OKD / OpenShift is used in many different cloud environments there are some popular solutions we may be asked to support.

One of them is IBM Cloud App Management (ICAM). There are others from other vendors.

So this issue suggests a change to our CRD, to allow for extensions to be added to our operator over time, increasing its out-of-the-box value add.

For example:

monitoring:
   prometheus:
     ....
monitoring:
   icam:
     ....

We should investigate if there's a way our operator can be backwards compatible with current CRs, so if one of the known types is not found under monitor we default to the current behaviour which is Prometheus.

@arthurdm arthurdm added the investigation Needs some investigation label Oct 29, 2019
@leochr leochr added the 0.5.0 label Feb 10, 2020
@leochr leochr added 0.6.0 and removed 0.5.0 labels Mar 26, 2020
@arthurdm arthurdm added future and removed 0.6.0 investigation Needs some investigation labels Apr 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants