Welcome to the Linux Foundation Forum!

Cannot curl on the public IP (Lab 2.3.14)

parinphatw
parinphatw Posts: 2
in LFD259 Class Forum

Hello,

Here are some of my configurations.

Infra: AWS EC2 (t2.medium) x2
OS: Ubuntu 20.04

I was following the lab along until 2.3.14.
After I created the service, I tried to curl with the public IP address of the CP node from my local terminal.

Like this: curl http://13.251.89.xx:31108

However, the curl was frozen and then returned the error back.

I was curious whether it's working or not, so I did curl with its internal IP within the Worker node and I could successfully get the result. But it did not happen to the CP.

Any suggestions why that happened and how to resolve it?

Answers

  • fazlur.khan
    fazlur.khan Posts: 73

    Hello @parinphatw

    Make sure your ports are open for incoming traffic.

    The ports are blocked, which is the cause of your inability to access. Open the ports in your aws console and this should work.

  • parinphatw
    parinphatw Posts: 2
    edited March 2023

    @fazlur.khan Thank you for your fast reply.

    Do you mean by the port on the security group?
    I already set the inbound rules to accept all connections from all ports.

  • chrispokorni
    chrispokorni Posts: 2,606

    Hi @parinphatw,

    If both EC2 instances are protected by the same SG, please provide the output of the following commands. In the past we experienced issues with Kubernetes components with EC2 instances smaller than t2.large:

    kubectl get nodes -o wide

    kubectl get pods -A -o wide

    Regards,
    -Chris

Categories

Upcoming Training