anchor.diff:  
   To set up and deploy the agent into your {product-title} cluster, run:
   ----
  -$ oc create -f hawkular-openshift-agent-configmap.yaml -n openshift-infra
  -$ oc process -f hawkular-openshift-agent.yaml | oc create -n openshift-infra -f -
  -$ oc adm policy add-cluster-role-to-user hawkular-openshift-agent system:serviceaccount:openshift-infra:hawkular-openshift-agent
  +$ oc create -f hawkular-openshift-agent-configmap.yaml -n default
  +$ oc process -f hawkular-openshift-agent.yaml | oc create -n default -f -
  +$ oc adm policy add-cluster-role-to-user hawkular-openshift-agent system:serviceaccount:default:hawkular-openshift-agent
   ----
   
   [[Undeploying-the-hawkular-openshift-agent]]
  
positive.code: 
  To undeploy the Hawkular Metrics Agent, run:
  ----
  $ oc delete all,secrets,sa,templates,configmaps,daemonsets,clusterroles --selector=metrics-infra=agent -n openshift-infra
  ----
  
  [[install-setting-the-metrics-public-url]]
  
negative.code: link:https://github.com/hawkular/hawkular-openshift-agent[Hawkular OpenShift
  Agent documentation].
  
  The agent runs as a daemon set in your cluster and is deployed to the `default`
  project. By deploying to the `default` project, the agent continues to monitor
  all your pods even if the `ovs_multitenant` plug-in is enabled.
  
  To deploy the agent, you will need to gather two configuration files:
  ifdef::openshift-origin[]
  ----
  