anchor.diff:  ====
   
   When the pod shown above runs against this new SCC (assuming, of course, the pod
  -has access to the new SCC), it will start because the group *5555*, supplied in
  +matches the new SCC), it will start because the group *5555*, supplied in
   the pod definition, is allowed by the custom SCC. Additionally, the pod will
   "take over" the block device, so when the block storage is viewed by a process
   outside of the pod, it will actually have *5555* as its group ID.
   
  -Currently the list of volumes which support block ownership (block) management
  -include:
  +A list of volumes supporting block ownership include:
   
   * AWS Elastic Block Store
   * OpenStack Cinder
  
positive.code: * emptyDir
  * gitRepo
  
  [[user-id]]
  == User IDs
  
  
negative.code: ====
  
  When the same pod shown earlier runs against this new SCC (assuming, of course,
  the pod matches the new SCC), it will start because the group *5555*,
  supplied in the pod definition, is now allowed by the custom SCC.
  
  [[fsgroup]]
  