Giter Club home page Giter Club logo

Comments (2)

ti-mo avatar ti-mo commented on July 3, 2024

@miminar Thanks for the report. Is this just the connectivity tests breaking, or NodePort breaking as a whole?

from cilium.

miminar avatar miminar commented on July 3, 2024

@miminar Thanks for the report. Is this just the connectivity tests breaking, or NodePort breaking as a whole?

It's not just the connectivity test. Although a connection to a node port always works from the host network, a connection from the pod network fails. And only for a particular node (the first one):

root@net-debug:/# for h in eu-k8s-dev-{01..10}.euler.ethz.ch; do curl -I --connect-timeout 1 http://$h:32346 |& grep '^HTTP' || echo "$h: BAD"; done
eu-k8s-dev-01.euler.ethz.ch: BAD
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK

Tested with services of type NodePort and LoadBalancer - same results. FWIW, the node has been re-added to the cluster:

$ kubectl get nodes
NAME                          STATUS   ROLES                   AGE     VERSION
eu-k8s-dev-01.euler.ethz.ch   Ready    compute,control-plane   2d20h   v1.30.1+k0s
eu-k8s-dev-02.euler.ethz.ch   Ready    compute,control-plane   17d     v1.30.1+k0s
eu-k8s-dev-03.euler.ethz.ch   Ready    compute,control-plane   17d     v1.30.1+k0s
eu-k8s-dev-04.euler.ethz.ch   Ready    compute                 2d20h   v1.30.1+k0s
eu-k8s-dev-05.euler.ethz.ch   Ready    compute                 16d     v1.30.1+k0s
eu-k8s-dev-06.euler.ethz.ch   Ready    compute                 16d     v1.30.1+k0s
eu-k8s-dev-07.euler.ethz.ch   Ready    compute                 16d     v1.30.1+k0s
eu-k8s-dev-08.euler.ethz.ch   Ready    compute                 16d     v1.30.1+k0s
eu-k8s-dev-09.euler.ethz.ch   Ready    compute                 9d      v1.30.1+k0s
eu-k8s-dev-10.euler.ethz.ch   Ready    compute                 9d      v1.30.1+k0s

But the same goes for eu-k8s-dev-04.euler.ethz.ch where this cannot be reproduced.

The connectivity test happens to choose the first node for the node port readiness check, that's why it fails reliably.

After a rollback to 1.15.4, I cannot reproduce anymore with any kind of node port.

from cilium.

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.