Giter Club home page Giter Club logo

Comments (12)

mcastelino avatar mcastelino commented on July 24, 2024

/cc @krsna1729

from cloud-native-setup.

mcastelino avatar mcastelino commented on July 24, 2024

This issue still exists with Installed version: 29880

from cloud-native-setup.

krsna1729 avatar krsna1729 commented on July 24, 2024
clear@clr-01 ~/clr-k8s-examples $ kubectl create deployment nginx --image=nginx
deployment.apps/nginx created
clear@clr-01 ~/clr-k8s-examples $ kubectl scale --replicas=3 deployment nginx
deployment.extensions/nginx scaled
clear@clr-01 ~/clr-k8s-examples $ for i in $(kubectl get pod -l app=nginx -o jsonpath='{.items[*].status.podIP}'); do curl -s -o /dev/null -w "%{http_code}\n" $i;  done
200
200
200
clear@clr-01 ~/clr-k8s-examples $ kubectl logs pod/nginx-65f88748fd-twq9k
10.244.0.0 - - [25/Jun/2019:20:11:10 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.65.1" "-"
clear@clr-01 ~/clr-k8s-examples $ swupd info
Installed version: 29880
clear@clr-01 ~/clr-k8s-examples $ /lib/systemd/systemd --version
systemd 241 (241)
clear@clr-01 ~/clr-k8s-examples $ kubectl run -i --tty busybox --image=busybox -- sh
kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead.
If you don't see a command prompt, try pressing enter.
/ #

from cloud-native-setup.

krsna1729 avatar krsna1729 commented on July 24, 2024

cluster was installed using ./create_stack.sh minimal

from cloud-native-setup.

mcastelino avatar mcastelino commented on July 24, 2024

This is due to the fact that the node IP is picked as as the private network even though the default route is setup to be on the public interface.

NAME     STATUS   ROLES    AGE    VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE         KERNEL-VERSION       CONTAINER-RUNTIME
clr-01   Ready    master   134m   v1.14.3   192.52.100.11   <none>        Clear Linux OS   4.19.48-48.lts2018   cri-o://1.14.1
clr-02   Ready    <none>   133m   v1.14.3   192.52.100.12   <none>        Clear Linux OS   4.19.48-48.lts2018   cri-o://1.14.1
clr-03   Ready    <none>   133m   v1.14.3   192.52.100.13   <none>        Clear Linux OS   4.19.48-48.lts2018   cri-o://1.14.1
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 1000
    link/ether 52:54:00:51:87:7c brd ff:ff:ff:ff:ff:ff
    inet 192.168.121.235/24 brd 192.168.121.255 scope global dynamic enp0s8
       valid_lft 2587sec preferred_lft 2587sec
    inet6 fe80::5054:ff:fe51:877c/64 scope link
       valid_lft forever preferred_lft forever
3: enp0s9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 1000
    link/ether 52:54:00:36:d1:d9 brd ff:ff:ff:ff:ff:ff
    inet 192.52.100.11/24 brd 192.52.100.255 scope global enp0s9
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fe36:d1d9/64 scope link
       valid_lft forever preferred_lft forever
default via 192.168.121.1 dev enp0s8 proto dhcp src 192.168.121.235 metric 1024
10.244.0.2 dev calid54f37530d0 scope link
10.244.1.0/24 via 10.244.1.0 dev flannel.1 onlink
10.244.2.0/24 via 10.244.2.0 dev flannel.1 onlink
192.52.100.0/24 dev enp0s9 proto kernel scope link src 192.52.100.11
192.168.121.0/24 dev enp0s8 proto kernel scope link src 192.168.121.235
192.168.121.1 dev enp0s8 proto dhcp scope link src 192.168.121.235 metric 1024

from cloud-native-setup.

mcastelino avatar mcastelino commented on July 24, 2024

nslookup is the only one that gives an incorrect response, which may be the issue.

clear@clr-01 ~/clr-k8s-examples $ nslookup clr-01
Server:         192.168.121.1
Address:        192.168.121.1#53

Non-authoritative answer:
Name:   clr-01
Address: 192.52.100.11

from cloud-native-setup.

mcastelino avatar mcastelino commented on July 24, 2024

Moving to latest kubernetes on clear still does not fix this issue. The node IPs are still setup on the non default route interface

clear@clr-01 ~/clr-k8s-examples $ ip route
default via 192.168.121.1 dev enp0s8 proto dhcp src 192.168.121.204 metric 1024
10.244.1.0/24 via 10.244.1.0 dev flannel.1 onlink
10.244.2.0/24 via 10.244.2.0 dev flannel.1 onlink
NAME     STATUS   ROLES    AGE     VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE         KERNEL-VERSION       CONTAINER-RUNTIME
clr-01   Ready    master   5m53s   v1.15.0   192.52.100.11   <none>        Clear Linux OS   4.19.57-60.lts2018   cri-o://1.14.4
clr-02   Ready    <none>   5m13s   v1.15.0   192.52.100.12   <none>        Clear Linux OS   4.19.57-60.lts2018   cri-o://1.14.4
clr-03   Ready    <none>   5m10s   v1.15.0   192.52.100.13   <none>        Clear Linux OS   4.19.57-60.lts2018   cri-o://1.14.4
clear@clr-01 ~/clr-k8s-examples $ swupd info
Installed version: 30270
Version URL:       https://cdn.download.clearlinux.org/update
Content URL:       https://cdn.download.clearlinux.org/update
clear@clr-01 ~/clr-k8s-examples $ kubelet --version
Kubernetes v1.15.0
clear@clr-01 ~/clr-k8s-examples $ kubectl run -i --tty busybox --image=busybox -- sh
kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead.
If you don't see a command prompt, try pressing enter.
Error attaching, falling back to logs: error dialing backend: EOF
Error from server: Get https://192.52.100.12:10250/containerLogs/default/busybox-5d847dfc85-27mp6/busybox: net/http: TLS handshake timeout

from cloud-native-setup.

NitinAtIntel avatar NitinAtIntel commented on July 24, 2024

Tested with multiple nics on two subnets, all 3 nodes including master were on those two subnets. Used create_stack to create cluster and resulting join command to join nodes. Was able to exec and see logs across the cluster (node to node). Currently, setup_system is set to user containerd. Tested both with containerd and modification back to use cri-o with same results. Recommend closing.

from cloud-native-setup.

ganeshmaharaj avatar ganeshmaharaj commented on July 24, 2024

@NitinAtIntel a quick Q.. were you able to exec into the container and land in it's shell? If yes, then i do agree to close this.

from cloud-native-setup.

NitinAtIntel avatar NitinAtIntel commented on July 24, 2024

@ganeshmaharaj I was able to get into busybox running on one of the nodes from master

from cloud-native-setup.

NitinAtIntel avatar NitinAtIntel commented on July 24, 2024

@ganeshmaharaj any further items to follow up on this or can we close?

from cloud-native-setup.

krsna1729 avatar krsna1729 commented on July 24, 2024

@NitinAtIntel closing it since this was only showing up in @mcastelino's vagrant environment. I had the same set of components still did not show up.

from cloud-native-setup.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.