anchor.diff:    - default
   ----
   
  +. *Deploy the Operator.* Use the files that were generated into the `deploy/`
  +directory by the Operator SDK when you built the Memcached Operator.
  +
   .. Apply the Operator's CSV manifest to the specified namespace in the cluster:
   +
   ----
  -$ curl -Lo memcachedoperator.0.0.1.csv.yaml https://raw.githubusercontent.com/operator-framework/getting-started/master/memcachedoperator.0.0.1.csv.yaml
  -$ oc apply -f memcachedoperator.0.0.1.csv.yaml
  -$ oc get csv memcachedoperator.v0.0.1 -n default -o json | jq '.status'
  +$ oc apply -f deploy/olm-catalog/memcached-operator/0.0.1/memcached-operator.v0.0.1.clusterserviceversion.yaml
   ----
   +
   When you apply this manifest, the cluster does not immediately update because
  
positive.code: application, in this case Memcached, as a whole. It is defined by a
  `ClusterServiceVersion` (CSV) object and is required for the OLM to function.
  +
  You can use the following command to generate CSV manifests:
  +
  ----
  $ operator-sdk olm-catalog gen-csv --csv-version 0.0.1
  ----
  +
  NOTE: This command is run from the `memcached-operator/` directory that was created when you built the Memcached Operator.
  +
  For the purpose of this guide, we will continue with this
  link:https://github.com/operator-framework/getting-started/blob/master/memcachedoperator.0.0.1.csv.yaml[predefined manifest file]
  for the next steps. You can alter the image field within this manifest to
  reflect the image you built in previous steps, but it is unnecessary.
  +
  [NOTE]
  ====
  
negative.code: for more information on manually defining a manifest file.
  ====
  
  . *Create an OperatorGroup* that specifies the namespaces that the Operator will
  target. Create the following OperatorGroup in the namespace where you will
  create the CSV. In this example, the `default` namespace is used:
  +
  