anchor.diff:  .Kubernetes Services
   image::../images/kubernetes-services.png[]
   
  -Any Service that a Pod wants to access must be created before the Pod itself, or else the environment variables will not be populated. 
  +NOTE: In this case, all the pods are running on a single minion. This is because, that is the default number for a Kubernetes cluster. The pod can very be on another minion if more minions exist in the cluster.
  +
  +Any Service that a Pod wants to access must be created before the Pod itself, or else the environment variables will not be populated.
   
   #### Start MySQL Service
   
  +. Start MySQL service as:
  ++
   [source, text]
   ----
   ./cluster/kubectl.sh create -f ../../attendees/kubernetes/mysql-service.yaml 
   ----
  -
  -Check that the service is created:
  -
  ++
  +. Check that the service is created:
  ++
   [source, text]
   ----
   > ./cluster/kubectl.sh get services
  
positive.code: NOTE: By default, only one minion is created. This can be manipulated by setting an environment variable NUM_MINIONS variable to an integer before invoking `kube-up.sh` script.
  +
  By default, each VM in the cluster is running Fedora, Kubelete is installed into ``systemd'', and all other Kubernetes services are running as containers on Master.
  
  
  ### Deploy Java EE Application
  
  
negative.code: ----
  +
  . Log out of master.
  
  #### Kubernetes Minion
  
  