Error while loading robusta-forwarder

[joseapeinado]

Describe the bug
Hi all, I'm having an issue with robusta installation using helm. The robusta-forwarder pod never becomes ready because of this:

time="2023-10-17T19:52:38Z" level=fatal msg="Can not get kubernetes config: stat //.kube/config: no such file or directory"

I've installed and configured Robusta using Helm using the official docs on an EKS cluster

To Reproduce
Steps to reproduce the behavior:
Just install robusta with Helm using the official docs.

Expected behavior
I guess the expected behavior is getting the robusta-forwarder pod working ok.

Screenshots

Additional context
I don't know if this could be related, but the EKS cluster is a little bit old (v1.21). Furthermore, I have information in the Robusta UI, Nodes info, and more, but for example I don't have any data on Timeline page.

[github-actions]

Hi 👋, thanks for opening an issue! Please note, it may take some time for us to respond, but we'll get back to you as soon as we can!

• 💬 Slack Community: Join Robusta team and other contributors on Slack here.
• 📖 Docs: Find our documentation here.
• 🎥 YouTube Channel: Watch our videos here.

[Sheeproid]

Hi @joseapeinado , thanks you for the patience on this. I'm consulting with the team.
I'm inviting you to join Robusta team and other contributors on Slack here. - we have a very active #support channel there.

[aantn]

Hey, we've looked into it and we're not sure what the issue is. Do you have any admission controls or policy engines in your cluster (e.g. kvyrno) that might modify the robusta-forwarder YAML before it runs?

That said, I think the issue with nothing showing up on the timeline is not 100% related. Do you use Prometheus, and if so is it our Prometheus or a Prometheus that was installed separately?

[joseapeinado]

Hi @aantn, no, we don't use these control policies on our cluster.
We deployed robusta using the --enable-prometheus-stack flag:

enablePrometheusStack: true

[aantn]

Hmm. Do you see anything on the timeline when following the below tutorial? https://docs.robusta.dev/master/tutorials/alert-builtin-enrichment.html If not, are there any errors in the logs for robusta-runner?

…

On Wed, Nov 1, 2023 at 2:05 PM Jose Peinado ***@***.***> wrote: Hi @aantn <https://github.com/aantn>, no, we don't use these control policies on our cluster. We deployed robusta using the --enable-prometheus-stack flag: enablePrometheusStack: true — Reply to this email directly, view it on GitHub <#1132 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADYUB34DR6WRY4RI73ZYQDYCI3IBAVCNFSM6AAAAAA6EP5VHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBYHA2DEMJYHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>