Giter VIP home page Giter VIP logo

Comments (6)

timothysc avatar timothysc commented on August 20, 2024

@cdelpinogeo Do you have the exact error you're seeing?

from contour.

davecheney avatar davecheney commented on August 20, 2024

Hi @cdelpinogeo

Thanks for raising this issue. I hope I don't sound like I'm passing the buck but this smells like a kubernetes bug. I say this because there's nothing special about contour, it's just a regular old deployment.

I'd try

kubectl delete -f https://j.hept.io/contour-deployment-rbac

Then

kubectl get ns -w

and wait for the heptio-contour namespace to disappear then

kubectl create -f https://j.hept.io/contour-deployment-rbac

If that doesn't seem to fix the problem, can you please paste the output of

kubectl get nodes

Thanks

Dave

from contour.

cdelpinogeo avatar cdelpinogeo commented on August 20, 2024

@timothysc, I've attached a screenshot of the error:

screenshot from 2017-12-13 22-07-51

There are no logged messages in the container:

screenshot from 2017-12-13 22-10-17

Thanks!

from contour.

cdelpinogeo avatar cdelpinogeo commented on August 20, 2024

@davecheney, thanks for following up. I've tried the steps you mentioned, but I get the same result. Here are the nodes:

NAME                             STATUS    ROLES     AGE       VERSION
ip-172-20-100-83.ec2.internal    Ready     node      6h        v1.8.4
ip-172-20-117-169.ec2.internal   Ready     master    6h        v1.8.4
ip-172-20-125-118.ec2.internal   Ready     node      6h        v1.8.4
ip-172-20-43-164.ec2.internal    Ready     node      6h        v1.8.4
ip-172-20-47-36.ec2.internal     Ready     node      6h        v1.8.4
ip-172-20-50-158.ec2.internal    Ready     master    7h        v1.8.4
ip-172-20-74-166.ec2.internal    Ready     node      6h        v1.8.4
ip-172-20-85-161.ec2.internal    Ready     master    6h        v1.8.4
ip-172-20-90-216.ec2.internal    Ready     node      6h        v1.8.4

Thanks again!

from contour.

davecheney avatar davecheney commented on August 20, 2024

@cdelpinogeo thanks for this information. Sadly I don't think I can assist you, that error is coming from the pod scheduler. Somehow your kubernetes thinks that node is still alive, even though it is not listed in get nodes.

from contour.

cdelpinogeo avatar cdelpinogeo commented on August 20, 2024

Thanks for looking into @davecheney. I decided to restart the masters, which fixed the issue. I'll raise this with the kops sig to see if this is an issue. Thanks!

from contour.

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.