A message for Linux.com registered users: We are in the process of making changes to the Linux forums. Starting Monday, 8/13/18 at 6:00 PM PT, you will be unable to access the forums. They will re-launch as soon as possible on Wednesday, 8/15/18 with new features and improved functionality. Thank you for your patience and stay tuned for the new improved forums.

Question on Lab 3.2 Step 10

I was trying the lab on AWS cloud. I successfully started a master and a node, and the node has successfully joined the cluster. However, when I start the deployment, there is no available nginx in the deployment.

=========== output ============

ubuntu@ip-10-0-0-69:~$ kubectl get deployments
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
nginx 1 1 1 0 23m

Comments

Please paste the output of kubectl get nodes, to ensure that both nodes have joined the cluster and are in good shape. As well, ensure that you have removed the taint on the master so that it is able to run non-internal pods?

As far as AWS, If you log into your console.aws.amazon.com page, navigate to Compute -> EC2 -> Instances -> Instances page you will see the running instances. Select the ones you want to work with then using the drop-down "Action" menu above you can perform actions to stop or terminate the instances. This tutorials covers the basic workflow/lifecycle of an instance: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html

In case you missed this earlier, I attempted the Labs from Chapter 3 on 2 EC2 instances on AWS and I did not run into any issues. In addition to possible join issue, or taints, as mentioned by @serewicz, I also researched the issue you have described, and I found several discussions on similar error/warning messages, and most of them suggest it may be networking related. It may have to do with the pod network used (Flannel, Calico) and/or the networking/firewall rules (security group, VPC, network ACL) configured for the EC2 instances.

I setup my 2 EC2's as Ubuntu VMs on t2.micro, with public IPs, inside a default security group where I opened all inbound TCP traffic (clearly not best practice, but for the purpose of these exercises it works).

Here is a list of ports used by Kubernetes which need to be open on each node: