anchor.diff:      referencePolicy:
         type: Local <2>
   ----
  -<1> Set tag *mytag* to use insecure connection to that registry.
  -<2> Set tag *mytag* to use integrated registry for pulling external images. If
  -the reference policy type is set to `*Source*`, clients fetch the image
  +<1> Set tag `mytag` to use an insecure connection to that registry.
  +<2> Set tag `mytag` to use integrated registry for pulling external images. If
  +the reference policy type is set to `Source`, clients fetch the image
   directly from `my.repo.com:5000/myimage`.
   ====
   
  
positive.code: 
  You can also add the `--scheduled=true` flag to have the destination tag be
  refreshed (i.e., re-imported) periodically. The period is configured globally at
  system level. See xref:importing-tag-and-image-metadata[Importing Tag and
  Image Metadata] for more details.
  
  If you want to instruct docker to always fetch the tagged image from the
  integrated registry, use `--reference-policy=local`. The registry will use
  xref:../install_config/registry/extended_registry_configuration.adoc#middleware-repository-pullthrough[pull-through
  feature] to serve the image to the client and by default, the image blobs will
  be mirrored locally by the registry. As a result, they will be available in
  shorter time next time they are needed. The flag also allows for pulling from
  insecure registries without a need to supply `--insecure-registry` to the
  Docker daemon if the image stream has an xref:insecure-registries[insecure
  annotation] or the tag has an xref:insecure-tag-import-policy[insecure import
  policy].
  
  [[tag-naming]]
  === Tag Naming
  
negative.code: If you require dates in tag names, periodically inspect old and unsupported
  images and _istags_ and remove them. Otherwise, you might experience increasing
  resource usage caused by old images.
  
  [[tag-removal]]
  === Removing Tags from Image Streams
  To remove a tag completely from an image stream run:
  