anchor.diff:  ```
   It will take a few minutes for the load balancer to be created and attached to the nodes.
   
  +== View the deployment as a service via a load balancer
  +
   In addition to seeing the hostname via the desribe operation, we can also retrieve just the hostname of the load balancer via:
   
       $ kubectl get service web -o jsonpath={.status.loadBalancer.ingress..hostname}
  
positive.code:     $ kubectl get service web -o jsonpath={.spec.ports..nodePort}
      32400
  
  Next, we need to open the port on the node itself to receive traffic that port. We do this by finding the security group to which the node belongs.
  
     $ aws ec2 describe-instances --filters "Name=private-dns-name,Values=ip-172-20-87-91.us-east-2.compute.internal" --query 'Reservations[*].Instances[*].SecurityGroups[*].GroupId'
      [
  
negative.code:     ]    
  
      $ aws ec2 authorize-security-group-ingress --group-id sg-c0285fa8 --protocol tcp --port 32400 --cidr 0.0.0.0/0
  
  Finally, we can use the AWS CLI to retrieve the public hostname of the node itself.
  
      $ aws ec2 describe-instances --filters "Name=private-dns-name,Values=ip-172-20-87-91.us-east-2.compute.internal" --query 'Reservations[*].Instances[*].NetworkInterfaces[*].PrivateIpAddresses[*].Association.PublicDnsName'
      [
  