Lab 3.2 Configure A Local Repo Step 3

stephansinn

I followed the course excactly as described.
I am using aws for my VMs and having a CP node and a Worker Node.
In AWS I adjusted the security tag in a way so that all ports are opened.

kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
basicservice NodePort 10.104.200.216 80:30735/TCP 36d
kubernetes ClusterIP 10.96.0.1 443/TCP 36d
nginx ClusterIP 10.107.140.85 443/TCP 44m
registry ClusterIP 10.97.40.62 5000/TCP 44m

But the curl for the registry endpoint is ending in a timeout. Why?

stephansinn

Ok I solved the issue. For all those also going through the training and using aws as VM provider:
Create your very own security group and allow all traffic from all ip addresses.
Specify this security group on instance creation or simply in your terraform file.

Caution: No Recommendation for any production setup. This is just the quickest way to rule out all possible aws network impediments that you might encounter during the course and does so distract you from the actual aim on learning k8s.

Remark: The Course should give a handout for the major IaaS provides on the market.

chrispokorni

Hi @stephansinn,

Perhaps the information that you seek is in the video demos from the introductory chapter - on how to provision the lab environment on AWS EC2 and Google GCE instances. The videos cover VPC, SG/firewall rules required for the lab VMs, together with the recommended VM size and guest OS.

Regards,
-Chris