Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Failed to get final advertise address: No private IP address found, and explicit IP not provided #615
Trying to replicate the example at https://github.com/improbable-eng/thanos/tree/master/kube#long-term-storage-setup on OpenShift 3.9. On a minishift envrionment it works, but on a managed setup I'm running into problems with the gossip component.
The sidecar is started with:
And the logs produce:
Being a bit more verbose doesnt improve things:
Seems thanos has problems binding to 0.0.0.0 ?!
Here is an internal e-mail thread on the same problem a couple of months ago:
Ok, so priv IP address is required for gossip cluster. And simply getting IP Address using
I would vote for number 3, especially when using kubernetes. The only question is that, how to turn off gossip logic for component. I think we need a PR for it with some flag