Don't deploy dependencies that are not used in a given deployment

[pwalsh]

Job story

When I deploy CCO into a cluster to provide multi-tenant management of CKAN, I want to be able to control the services that are deployed, so that I do not run services I do not use and that services I do not use do not consume cluster resources.

Context

The code base has services running (ELK?), Minio, that may not be in use on a given CCO deployment.

Acceptance criteria

• [ ] Run a command or a set of commands to see what services exactly are being deployed in a CCO managed cluster to support multi-tenant CKAN
• [ ] Ability in cone/configuration to enable/disable certain services
  • Monitoring of the cluster itself
  • Software that supports CCO actions (e.g: Jenkins)
  • Subservices to support CKANs deployed in cluster
• [ ] Documentation on how to enable/disable deployment of certain services

[pwalsh]

@akariv a first step may be an audit of exactly what does currently get deployed and towards what purpose.

[pwalsh]

@akariv @zelima this is assigned to @aluminiumgeek

is this still to be done?