anchor.diff:  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.
  -
  ++
  +. Access `https://10.245.1.2` (or whatever IP address is assigned to your kubernetes cluster start up log). This may present the warning as shown below:
  ++
  +image::../images/kubernetes-master-default-output-certificate.png[]
  ++
  +Click on ``Advanced'' and then on ``Proceed to 10.245.1.2'' to see the output as:
  ++
  +.Kubernetes Output from Master
  +image::../images/kubernetes-master-default-output.png[]
   
   ### Deploy Java EE Application
   
  
positive.code: .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. 
  
  #### Start MySQL Service
  
  [source, text]
  ----
  ./cluster/kubectl.sh create -f ../../attendees/kubernetes/mysql-service.yaml 
  ----
  
  Check that the service is created:
  
  [source, text]
  ----
  > ./cluster/kubectl.sh get services
  
negative.code: +
  The `KUBERNETES_PROVIDER` environment variable tells all of the various cluster management scripts which variant to use.
  +
  NOTE: This will take a few minutes, so be patience! Vagrant will provision each machine in the cluster with all the necessary components to run Kubernetes.
  +
  It shows the output as:
  +
  [source, text]
  ----
  