Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Ciaran
    @ciaranlangton
    the first one is a database, which has worked fine over the LB for ~4 weeks now with no issue, but adding the second port stops the LB from being completed on OVH's end
    Michał Frąckiewicz
    @SystemZ
    some range of ports were reserved maybe you just run over them
    Ciaran
    @ciaranlangton
    yeah, I'll try some other ports and report back
    Michał Frąckiewicz
    @SystemZ
    if you leave one port it works ok ?
    Ciaran
    @ciaranlangton
    correct, the first port has been there for ~4 weeks fully functional
    Michał Frąckiewicz
    @SystemZ
    oh, maybe it's some bug or LB doesn't support more than one port, hard to tell
    Ciaran
    @ciaranlangton
    I just took the second one out now, and it ensures properly
    Normal EnsuredLoadBalancer 3s service-controller Ensured load balancer
    Yeah, I read the docs and it said that there were a maximum of 6 ports on an LB
    maybe the problem only occurs when adding new ports to an already existing LB
    since I've had other LBs with multiple ports before, just that they were initialized with that number of ports
    Michał Frąckiewicz
    @SystemZ
    yea, maybe launch just new with those ports
    if not, you should wait for some ovh team online :)
    Michał Frąckiewicz
    @SystemZ
    image.png
    I again encountered problem with adding node to my empty sandbox cluster 1b5e5c98-023e-4891-8887-2f3ac6336c64.
    When I clicked "upgrade minor version" during this freeze I've got error 500
    Thomas Coudert
    @thcdrt
    Hello @SystemZ, checking.
    The 500 error should be a 400 error instead. You can't upgrade you cluster while a node is installing
    Michał Frąckiewicz
    @SystemZ
    thx, yea I just assumed that error 500 is not desired for this edge case
    Thomas Coudert
    @thcdrt
    Yes sorry about that.. We'll fix that asap
    Hello @ciaranlangton , indeed you should be able to create LBs with 2 ports. Can you give me your cluster-id in private to allow me to dig into logs ? Thanks
    Bmagic
    @bmagic
    Hello this morning I have one of my pod in "InvalidNodeInfo" state. Any idea what could cause this kind of issue ?
    Bmagic
    @bmagic
    Ok I have some strange log message on logs metrics server : 
    E0915 10:32:05.134618       1 summary.go:97] error while getting metrics summary from Kubelet node-c4260b85-c8c7-4f7d-88e9-id( [IP]:10250): Get https://[IP]:10250/stats/summary/: dial tcp [IP]2:10250: getsockopt: no route to host
    Nicolas Steinmetz
    @nsteinmetz
    @MrDienns did you check the Certificate object was celle created first ? (kubectl describe secrets/YourCertificate if I remember well ?)
    @MrDienns so all is working ? sorry I spent most of my week-end in the garden :-)
    Thomas Coudert
    @thcdrt
    Hello @bmagic , can you send me in private your cluster id and the node IP please ?
    Michał Frąckiewicz
    @SystemZ
    any tips how to get all container logs sent to ovh log data platform?
    I'm searching for something similar to this but with TLS output
    https://github.com/roffe/kube-gelf
    as far as I know, logstash doesn't support TLS for GELF protocol as input and fluentd doesn't support syslog output <facepalm>
    Joël LE CORRE
    @jlecorre_gitlab
    Hello @SystemZ Maybe this documentation can help you?
    I'm not sure if it meets your needs: https://docs.ovh.com/fr/logs-data-platform/kubernetes-fluent-bit/
    Michał Frąckiewicz
    @SystemZ
    Looks promising, I'll check it :)
    Jawher Moussa
    @jawher_twitter
    Hi ! I tried to follow the fluent-bit tutorial above, but it references the tag fluent/fluent-bit:1.3, but that version does not exist (the daemonset pods fail with ImagePullErr. According to dockerhub, the latest version is 1.2.2.
    Using that version (1.2), the fluent-bit pods continuously log [2019/09/17 12:01:58] [error] [out_gelf] error encoding to GELF
    Michał Frąckiewicz
    @SystemZ
    Yeah, I encountered this too
    I tried :latest version of image and it didn't work either
    Thomas Coudert
    @thcdrt
    Hi @jawher_twitter , checking with the Logs team
    Jawher Moussa
    @jawher_twitter
    Thanks 🤗
    Michał Frąckiewicz
    @SystemZ
    it's probably related to filter-kubernetes.conf
    fluent/fluent-bit#1070
    Thomas Coudert
    @thcdrt
    Yes, there is an issue on the 1.2 version that has been fixed on master but which is not yet released.
    We're seeing how we can get around the problem until this modification has been prodded
    Michał Frąckiewicz
    @SystemZ
    I'll try to build docker image from master
    Jawher Moussa
    @jawher_twitter
    Thank you @thcdrt , I appreciate the prompt response ! I'll try building fluentbit from master :+1:
    Thomas Coudert
    @thcdrt
    Ok @jawher_twitter , keep me updated :)
    Michał Frąckiewicz
    @SystemZ
    I'll already pushed it systemzz/fluent-bit:latest
    so far it doesn't show that error, I'll check if logs are being sent
    yep, it works, only docker image needs to be changed
    no errors, logs visible in graylog
    Thomas Coudert
    @thcdrt
    Great, thanks @SystemZ :)
    We will push it on one of our repo and modify doc until fluentbit release its new version
    Michał Frąckiewicz
    @SystemZ
    :thumbsup:
    Michał Frąckiewicz
    @SystemZ
    I see that calico-node is pretty chatty, any idea how to ignore containers from sending logs to graylog ?