Details
-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
None
-
False
-
NetObserv - Sprint 244, NetObserv - Sprint 245, NetObserv - Sprint 246
Description
The issue with configuring limits via CSV as we suggest here https://docs.openshift.com/container-platform/4.13/network_observability/troubleshooting-network-observability.html#controller-manager-pod-runs-out-of-memory_network-observability-troubleshooting is that, on the next operator upgrade, the CSV is going to be replaced, hence users loose their limits configuration.
The "correct" way of doing it is by configuring limits on Subscription: as explained here https://docs.openshift.com/container-platform/4.13/operators/admin/olm-adding-operators-to-cluster.html#olm-installing-operator-from-operatorhub-using-cli_olm-adding-operators-to-a-cluster
Example of Subscription yaml with the resources configuration (memory limit raised to 800MB) :
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.v1.4.1