anchor.diff:  
   === Create your first pod
   
  -This command creates an nginx pod into your cluster:
  +This command instantiates an nginx container into your cluster, inside a pod:
   
       $ kubectl run nginx --image=nginx
       deployment "nginx" created
  
positive.code:     $ kubectl get pods
      $ kubectl exec -it <pod-name> /bin/bash
  
  This opens a Bash shell and allows you to look around the filesystem of the container.
  
  == Expose the deployment as a service (via NodePort)
  
  By default, all Kubernetes resources are only accessible within the cluster. This command will create a loadBalancer and allow the the NGiNX deployment to be accessible from the Internet:
  
      $ kubectl expose deployment nginx --type=NodePort --port=80 --target-port=80 --name=web
      service "web" exposed
  
  This will expose the deployment as a Service. You can see the published service:
  
      $ kubectl get service
      NAME         TYPE           CLUSTER-IP      EXTERNAL-IP        PORT(S)        AGE
  
negative.code:             "sg-c0285fa8"
          ]
      ]    
  
  Next, we add an ingress rule to the security group opening up the port on the node to anyone - `0.0.0.0/0`. This is purely for demonstration purposes in this workshop and is not a best practice. Most services will be exposed behind a load balancer, which we cover in the next section.  For the command below, replace the `--port` flag value with the nodePort retreived above.
  
      $ aws ec2 authorize-security-group-ingress --group-id sg-c0285fa8 --protocol tcp --port 32400 --cidr 0.0.0.0/0
  
  