anchor.diff:  
   A picture is always worth a thousand words and so this is a high-level logical block diagram for Kubernetes:
   
  +.Kubernetes Key Concepts
   image::../images/kubernetes-key-concepts.png[]
   
   After the 50,000 feet view, lets fly a little lower at 30,000 feet and take a look at how Kubernetes make all of this happen. There are a few key components at Master and Minion that make this happen.
  
positive.code: ----
  +
  . Log out of master.
  . Access `https://10.245.1.2` (or whatever IP address is assigned to your k8s cluster start up log) to see the output as:
  +
  image::../images/kubernetes-master-default-output.png[]
  
  #### Kubernetes Minion
  
negative.code: 
  Kubernetes services is an abstraction which defines a logical set of pods. A service is typically back-ended by one or more physical pods (associated using labels), and it has a permanent IP address that can be used by other pods/applications. For example, WildFly pod can not directly connect to a MySQL pod but can connect to MySQL service. In essence, Kubernetes service offers clients an IP and port pair which, when accessed, redirects to the appropriate backends.
  
  .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. 
  