sebastienle14

greetings @neoaggelos Indeed, I can: ``` root@host:~# ip route show default via 192.168.100.1 dev net100 proto static 192.168.100.0/24 dev net100 proto kernel scope link src 192.168.100.56 192.168.102.0/24 dev net102 proto...

I believe this output shall be necessary too, sorry I forgot to add it in OP: ``` root@eck-master:~# kubectl get svc -o wide -n eck NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S)...

Our Hosting team confirms all networking the host is plugged to are managed by a CISCO Nexus 3064-T, 48 x 10GBase appliance, which should be manageable but they know nothing...

> I see the nmap, can you also try a curl? Here it is: ``` root@host:~# curl https://192.168.100.100:30932/ --insecure curl: (28) Failed to connect to 192.168.100.100 port 30932: Connection timed...

The captures are too big to be fit for attachement here, so I create this wetransfer link: https://we.tl/t-p8xP4Zkyfy On host, I used: `tcpdump -i any -n not tcp port 22...

> How about curl https://192.168.100.70:30932 (on the IPs of the nodes directly)? From the node itself: ``` root@eck-master:~# curl https://192.168.100.70:30932 --insecure 404 Not Found 404 Not Found nginx ``` From...

as a follow-up: cross-nodes, the curl on 30932 is not working, but it works on each node querying itself ``` root@eck-master:~# kubectl -n eck get svc NAME TYPE CLUSTER-IP EXTERNAL-IP...

I will try & setup the cluster accordinly, but it might take some time; I do not know if the ticket may be put on hold until monday or so...

Greetings, So we tried to set-up a POC environnement, and so far, we failed to even deploy the LoadBalancer (keeps in Pending Status) poc-master on virbr0 with 192.168.122.193 poc-worker01 on...

@neoaggelos I'll also add our netplan config file from the host to the discussion: ``` ~# cat /etc/netplan/00-installer-config.yaml network: version: 2 renderer: networkd ethernets: eno1: dhcp4: false dhcp6: false match:...