We would like the CLO to handle the lifecycle of our log-exploration-api in the same way CLO handles the fluentd for example.
The following changes should be made:
- CLO will spin up log-exploration-api instance only elasticsearch is deployed (default configuration)
- CLO should know which image to use (see clusterserviceversion env parameters for the cluster-logging-operator container)
- Unit tests added
- E2E test added