$ oc get csvs -n openshift
The Operator Lifecycle Manager (OLM) controller is configured by an
OLMConfig custom resource (CR) named
cluster. Cluster administrators can modify this resource to enable or disable certain features.
This document outlines the features currently supported by OLM that are configured by the
When an Operator is installed by Operator Lifecycle Manager (OLM), a simplified copy of its cluster service version (CSV) is created by default in every namespace that the Operator is configured to watch. These CSVs are known as copied CSVs and communicate to users which controllers are actively reconciling resource events in a given namespace.
When an Operator is configured to use the
AllNamespaces install mode, versus targeting a single or specified set of namespaces, a copied CSV for the Operator is created in every namespace on the cluster. On especially large clusters, with namespaces and installed Operators potentially in the hundreds or thousands, copied CSVs consume an untenable amount of resources, such as OLM’s memory usage, cluster etcd limits, and networking.
To support these larger clusters, cluster administrators can disable copied CSVs for Operators globally installed with the
If you disable copied CSVs, an Operator installed in
OLMConfig object named
cluster and set the
spec.features.disableCopiedCSVs field to
$ oc apply -f - <<EOF apiVersion: operators.coreos.com/v1 kind: OLMConfig metadata: name: cluster spec: features: disableCopiedCSVs: true (1) EOF
|1||Disabled copied CSVs for
When copied CSVs are disabled, OLM captures this information in an event in the Operator’s namespace:
$ oc get events
LAST SEEN TYPE REASON OBJECT MESSAGE 85s Warning DisabledCopiedCSVs clusterserviceversion/my-csv.v1.0.0 CSV copying disabled for operators/my-csv.v1.0.0
spec.features.disableCopiedCSVs field is missing or set to
false, OLM recreates the copied CSVs for all Operators installed with the
AllNamespaces mode and deletes the previously mentioned events.