anchor.diff:  
   ====
   
  -=== Setting the endpoints
  +=== Setting the Endpoints
   
   The next step is to create endpoints for the service. This gives information about where to send traffic going to the
   service to the service proxy and router.
  
positive.code: <1> The name of the `Service` instance.
  <2> Traffic to the service is load-balanced between the `Endpoints` supplied here.
  
  === Consuming credentials in pods
  
  Now that the service and endpoints are defined, give pods the credentials to use the service. This is done
  by setting environment variables in the appropriate containers. 
  
negative.code: applications can work with them as they would any other internal service.
  
  
  == External MySQL Database
  
  One of the most common types of external services is an external database. To support an external database, an application needs:
  
  1. An endpoint to communicate with.
  2. A set of credentials and coordinates. Including:
     a.  A username
     b.  A passphrase
     c.  A database name
  
  The solution for integrating with an external database includes:
  
  1.  A `Service` object to represent the SaaS provider as an OpenShift service
  2.  One or more `Endpoints` for the service
  3.  Environment variables in the appropriate pods containing the credentials
  
  === Creating the Service
  
  The first step in integrating with an external service is to create an OpenShift service to
  represent it. This is similar to creating an internal service; the difference is in the
  service's `Selector` field.
  
  Internal OpenShift services use the `Selector` field to associate pods with services
  via labels. A system component called `EndpointsController` synchronizes the endpoints for
  services that specify selectors with the pods that match the selector. The service proxy and
  OpenShift router load-balance requests to the service amongst the service's endpoints.
  
  The only difference between an internal OpenShift service and a service that represents an external
  resource is that there are no pods to associate an external service with. To represent external
  services, we just need to leave the `Selector` field unset. This will make the `EndpointsController`
  ignore the service and allow you to specify endpoints manually:
  
  ====
  
  ----
  {
  