ONAP may be deployed in various sizes and configurations. The default ONAP install should be tailored to deploy on a single kubernetes node with as few required resources as possible. As such, clustering should be turned off for all components. A customized override configuration can then be applied to create a larger production grade deployment which enables HA and clustering capabilities.

The output of this defect is to deliver a configuration override file such as onap/resources/environment/production.yaml.

This file would contain overrides to enable cluster, set resource limits (i.e. cpu, memory, etc. per pod), etc. The eventual goal would be to have multiple production.yaml type files, each tailored for each ONAP use case that we want to run.