anchor.diff:  further specify TLS options and a certificate, or specify a public CNAME that
   the OpenShift Ingress Controller should also accept for HTTP and HTTPS traffic.
   An administrator typically configures their Ingress Controller to be visible
  -outside the cluster firewall, and may also add additional security, caching, or
  +outside the cluster firewall, and might also add additional security, caching, or
   traffic controls on the service content.
   
   ''''
  
positive.code: == L
  
  == M
  
  ''''
  === minion
  
negative.code: 
  OpenShift-specific API object that allows developers to expose services through
  an HTTP(S) aware load balancing and proxy layer via a public DNS entry. The
  route might further specify TLS options and a certificate, or specify a public
  CNAME that the OpenShift Ingress Controller should also accept for HTTP and
  HTTPS traffic. An administrator typically configures their Ingress Controller to
  be visible outside the cluster firewall, and might also add additional security,
  caching, or traffic controls on the service content.
  
  == S
  