Welcome to the Linux Foundation Forum!

Lab 3.4-5

Hello,
The labs are Ok but i've collected several questions :)
1. How is ClusterIP assigned ? There is no info inside the calico.yaml. Probably the range is 10.0.0.0/8 ; Is it possible to configure - where?
2. The endpoints IP are from 192.168.0.0/16 range (calico.yaml). What about the following IP address:
kubectl exec nginx-6d48c9bcb8-5wlwp -- printenv | grep KUBERNETES ?? It seems 10.96.0.0/16. How is the IP assigned ?
What is the different between the epIP and 10.96.0.0/16 ?
3. As for lab 3.5 task 5, we create a new type of NGINX --> load-balance. I can make an access outside my cluster with IP of my NIC + the port. It's Ok. What about access to Web server (the lab 3.4 task 15). I can use the curl on the master node .It's Ok. Why cannot I use my NIC_IP:80 to access to the web-server ?
4. As for 3.5 task 9, we delete deployment + ep + service but we don't create ep+service. Does It mean as soon as a deployment is created ep/service are created too ?

May you have any links or materials about IP addresses of Kubernetes ?
Thank you in advance.
Alexey

Comments

  • AlexeyBY
    AlexeyBY Posts: 56
    edited February 2021

    Hello again,
    May add a comment here. Pls see Chapter 4 of the course Container to Outside Path.
    We can see the one endpoint IP per a pod -> 192.168.1.27. --> Even though there are two containers, they share the same namespace and the same IP address!!

    Pls see also chapter 3.4 task 22 . There are three IP addresses here. One IP is per the NGINX containers. Can you explain why ?

    Thank you

  • I"m having issues with lab 3.5. I'm using AWS. The instructions say to use the public ip i use to ssh but the ssh command is:
    ssh -i student.pem ubumtu@ec2-3.138....us-east-2.compute.amazonaws.com. So do i use everything after the @ sign or just the numbers for the ip. Keep in mind AWS uses - instead of . in the ip addresses. My error is just "This site Can't be reached."

  • chrispokorni
    chrispokorni Posts: 2,606
    edited February 2021

    Hi @kstand1ge,

    IPv4 IP addresses are in the format of 35.45.55.65 regardless of the cloud provider. What you see on AWS the ...35-45-55-65... format is just the hostname of the EC2 VM instance. For ssh you can use either the IPv4 IP address or the public DNS displayed in the AWS EC2 dashboard.

    Regards,
    -Chris

  • i've tried both and neither work. I still get the same error. 3.138.102.218 refused to connect. I've done something wrong somewhere, i guess. is there something i need to do on the AWS side?

  • chrispokorni
    chrispokorni Posts: 2,606
    edited February 2021

    Hi @kstand1ge,

    There is a setup video for AWS EC2 instances that you can access from the Course Resources page of Chapter 1.

    Regards,
    -Chris

  • yeah, i did that twice. I don't know what i've done wrong but it isn't working. I'm on a mac so the putty stuff doesn't really help me.

  • @kstand1ge, then run the ssh command in a terminal, or connect to your instance directly from the AWS EC2 dashboard.

  • well, i did that. I'm on my instances. No worries there. it's trying to access nginx externally where i'm getting the issue. lab 3.5.

  • chrispokorni
    chrispokorni Posts: 2,606
    edited February 2021

    @kstand1ge, without seeing the actual errors it is difficult to diagnose your specific issue. In the forum you can find prior discussions reporting several issues on AWS EC2 instances, together with solutions on how to fix them.

    Regards,
    -Chris

Categories

Upcoming Training