1. Proposed title of this feature request
2. What is the nature and description of the request?

• Support Case, feature request.
  3. Why does the customer need this? (List the business requirements here):

• In order to automate the deployment of this operator using CI/CD

4. List any affected packages or components.

• Network Observability Operator

Notes:

• Documentation says that the network Observability controller manager  memory deployment depends on the cluster size.

The actual memory consumption of the Operator depends on your cluster size and the number of resources deployed. Memory consumption might need to be adjusted accordingly. For more information refer to "Network Observability controller manager pod runs out of memory" in the "Important Flow Collector configuration considerations" section. 

• At this point, this value only could be modified after operator's initial deployment by applying the workaround described when at [Network Observability controller manager pod runs out of memory

  https://docs.openshift.com/container-platform/4.13/network_observability/troubleshooting-network-observability.html#controller-manager-pod-runs-out-of-memory_network-observability-troubleshooting]

• This is a limitation when customers try to make the initial deployment using ArgoCD.
• This value should be auto-adjusted based on the cluster-size while the initial deployed or at least customizable from the installation.