anchor.diff:  [id="csi-example-deployment_{context}"]
   = Example CSI deployment
   
  -Since {product-title} does not ship with any CSI driver installed, this 
  -example shows how to deploy a community driver for OpenStack Cinder in 
  +Since {product-title} does not ship with any CSI driver installed, this
  +example shows how to deploy a community driver for OpenStack Cinder in
   {product-title}.
   
   .Procedure
   
   . Create a new project where the CSI components will run, and then create
  -a new service account to run the components. An explicit node selector is 
  +a new service account to run the components. An explicit node selector is
   used to run the Daemonset with the CSI driver also on master nodes.
   +
   ----
   # oc adm new-project csi --node-selector=""
  -Now using project "csi" on server "https://example.com:8443".
  +Created project csi
   
   # oc create serviceaccount cinder-csi
   serviceaccount "cinder-csi" created
   
   # oc adm policy add-scc-to-user privileged system:serviceaccount:csi:cinder-csi
  -scc "privileged" added to: ["system:serviceaccount:csi:cinder-csi"]
  -----
  -
  -. Apply this YAML file to create the deployment with the external CSI 
  +securitycontextconstraints.security.openshift.io/privileged added to: ["system:serviceaccount:csi:cinder-csi"]
  +----
  +
  +. Apply this YAML file to create the deployment with the external CSI
   attacher and provisioner and DaemonSet with the CSI driver.
   +
   [source,yaml]
  
positive.code:             - name: socket-dir
                mountPath: /csi
          - name: csi-provisioner
            image: registry.redhat.io/openshift/csi-provisioner:v4.0
            args:
              - "--v=5"
              - "--provisioner=csi-cinderplugin"
  
negative.code:       serviceAccount: cinder-csi
        containers:
          - name: csi-driver-registrar
            image: quay.io/k8scsi/csi-node-driver-registrar:v1.0.2
            securityContext:
              privileged: true
            args:
  