anchor.diff:  files can be obtained through https://access.crunchydata.com/ on the downloads
   page.*
   
  -=== Creating a Demo Namespace on Kubernetes
  +=== Creating a Demo Namespace
  +
  +In Kubernetes, a concept called a *namespace* provides the means to separate
  +created resources or components into individual logically grouped partitions.
  +
  +It is considered a best practice to have dedicated namespaces for projects in
  +both testing and production environments.
  +
  +NOTE: All examples in the Crunchy Container Suite operate within the namespace
  +defined by the environment variable `$CCP_NAMESPACE`. The instructions below
  +illustrate how to set up and work within new namespaces or projects in both
  +Kubernetes and OpenShift.
  +
  +==== Kubernetes
   
   This section will illustrate how to set up a new Kubernetes namespace called *demo*, and will
   then show how to provide permissions to that namespace to allow the Kubernetes examples to run
  -within that namespace. This is a *requirement* for running the examples.
  +within that namespace.
   
   First, view currently existing namespaces:
   ....
  
positive.code: export CCP_STORAGE_CAPACITY=400M
  ....
  
  === Configure NFS for Persistence
  
  NFS can be used for the examples as well.  Instructions
  on setting up NFS are found at the bottom of this guide.
  
  For testing with NFS, in your *.bashrc* file, include
  
negative.code: oc login -u someuser
  ....
  
  For our development purposes only, we typically specify the OCP
  Authorization policy of *AllowAll* as documented here:
  
  https://docs.openshift.com/container-platform/3.7/install_config/configuring_authentication.html#AllowAllPasswordIdentityProvider
  