Let's talk about our Kubernetes As a Service Product #OVH
People
Repo info
Activity
Michał Frąckiewicz
@SystemZ
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.1346181 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?
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