Red Hat OpenShift Container Platform

Network observability controller manager pod runs out of memory

Resolve memory issues with the Network Observability Operator by increasing the memory limits in the Subscription object to prevent the controller manager pod from running out of memory.

You can increase memory limits for the Network Observability Operator by editing the spec.config.resources.limits.memory specification in the Subscription object.

Procedure

In the web console, navigate to Ecosystem → Installed Operators
Click Network Observability and then select Subscription.
From the Actions menu, click Edit Subscription.
1. Alternatively, you can use the CLI to open the YAML configuration for the Subscription object by running the following command:
  $ oc edit subscription netobserv-operator -n openshift-netobserv-operator

Edit the Subscription object to add the config.resources.limits.memory specification and set the value to account for your memory requirements. See the Additional resources for more information about resource considerations:

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: netobserv-operator
  namespace: openshift-netobserv-operator
spec:
  channel: stable
  config:
    resources:
      limits:
        memory: 800Mi     
      requests:
        cpu: 100m
        memory: 100Mi
  installPlanApproval: Automatic
  name: netobserv-operator
  source: redhat-operators
  sourceNamespace: openshift-marketplace
  startingCSV: <network_observability_operator_latest_version>

	For example, you can increase the memory limit to `800Mi`.
	This value should not be edited, but note that it changes depending on the most current release of the Operator.