-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed to create memberlist: Failed to get final advertise address: no private IP address found, and explicit IP not provided #8634
Comments
I have the same issue i think. When trying to install the loki-stack on GKE.
|
Same here on EKS:
|
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This is a follow up to #6370. I believe there's something that needs to be fixed to work with different network configurations instead of forcing a workaround so that other users like me don't encounter the same issue on a simple base installation.
I have kube-prometheus-stack installed with metrics and grafana dashboards functional. I want to install loki to add functionality to see my pods logs. To be honest being new to this ecosystem I'm a bit confused about the dozens of different helm charts available and which is the proper one for my simple needs. I first tried with
loki-stack
(since it comes bundled with promtail) and then withloki-simple-scalable
(based on this guide) and they both have the same issue.#6370 offers a workaround by providing the pod IP as an environment variable and using it back in the loki config. Unfortunately I believe this workaround require us to download the chart locally and modifying it, and can't be just fixed providing a values.yaml. It also apply to the base loki chart (the "expert" configuration) and doesn't work as-is with the simple charts mentioned above.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Environment:
Screenshots, Promtail config, or terminal output
The text was updated successfully, but these errors were encountered: