anchor.diff:  kind: Service
   metadata:
     name: egress-1
  -spec: 
  +spec:
     ports:
     - name: db
       port: 3306
  
positive.code: IP address of 172.7.7.7.
  
  `MongoDB service A` requests port 27017, and then
  `MongoDB service B` requests the same port; the first request gets the port. 
  ====
  
  However, port clashes are not an issue for external IPs assigned by the ingress
  
negative.code: toc::[]
  
  == Overview
  
  Note: This feature is only supported in non-cloud deployments.  For
  cloud (GCE/AWS/OpenStack) deployments, services of type
  xref:../dev_guide/getting_traffic_into_cluster.adoc#using-the-loadbalancer[LoadBalancer]
  can be used to automatically deploy a cloud loadbalancer to target the
  service's endpoints.
  
  Cluster administrators can assign a unique external IP address to a service. If
  routed correctly, external traffic can reach that service's endpoints via any
  